This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: patch: cleanup gcc.dg/vect/


mipsisa64*-*-* only supports V2SF mode (two single floating point in
parallel).
If tests try to vectorize integer code, these tests will fail on
mipsisa64*-*-*.
So, mipsisa64*-*-* is specified in 31 tests that vectorize the float array
only.

Regards,
Chao-ying

----- Original Message ----- 
From: "Janis Johnson" <janis187@us.ibm.com>
To: "Janis Johnson" <janis187@us.ibm.com>
Cc: "Aldy Hernandez" <aldyh@redhat.com>; <gcc-patches@gcc.gnu.org>;
<dorit@il.ibm.com>
Sent: Monday, October 18, 2004 4:54 PM
Subject: Re: patch: cleanup gcc.dg/vect/


> On Mon, Oct 18, 2004 at 03:06:09PM -0700, Janis Johnson wrote:
> > On Mon, Oct 18, 2004 at 03:41:19PM -0400, Aldy Hernandez wrote:
> > > I have also disabled the powerpc tests when VMX is not available.
Right
> > > now, we indiscriminately try to run tests when hardware may not be
> > > available.
> > >
> > > I am not sure if we may still want to run the tests, especially the
compile
> > > tests even if the HW is not available.  Dorit?  Folks?  If this is the
> > > case, then we can just disable the tests for powerpc-*-*spe.
> >
> > Compiling and the checks in the dg-final step are useful, so perhaps we
> > can change the "dg-do" option from "run" to "compile" if the hardware
> > doesn't have vector support, as is done for the gcc.dg/vmx tests.  I'll
> > take a look and let you know if it will fit in nicely with the vect test
> > infrastructure.
>
> I'm making progress but have questions for Dorit and others who have
> contributed the vect tests:
>
> Tests vect-72.c and vect-73.c use -mpowerpc64.  That has no effect on a
> biarch compiler; should it have been -m64?  I always test a biarch
> compiler with both -m32 and -m64 anyway so using -m64 in a test would
> cause problems, or at least confusion.  There are tests in other parts
> of the testsuite that are only relevant for either -m32 or -m64 that
> we're trying to figure out how to handle.
>
> There are currently 91 tests in gcc.dg/vect and only 31 of them specify
> mipsisa64*-*-* as a target.  Is it an oversight that most of the other
> tests are not run for mipsisa64?
>
> Janis
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]