This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: patch: cleanup gcc.dg/vect/
- From: Janis Johnson <janis187 at us dot ibm dot com>
- To: Janis Johnson <janis187 at us dot ibm dot com>
- Cc: Aldy Hernandez <aldyh at redhat dot com>, gcc-patches at gcc dot gnu dot org, dorit at il dot ibm dot com
- Date: Mon, 18 Oct 2004 16:54:44 -0700
- Subject: Re: patch: cleanup gcc.dg/vect/
- References: <20041018194119.GA10231@redhat.com> <20041018220609.GA26745@us.ibm.com>
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