This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [testsuite] (checked in) fix gcc.dg/vect/vect-dv-2.c
- From: Janis Johnson <janis187 at us dot ibm dot com>
- To: Giovanni Bajo <giovannibajo at libero dot it>
- Cc: Janis Johnson <janis187 at us dot ibm dot com>, gcc-patches at gcc dot gnu dot org
- Date: Fri, 20 May 2005 09:06:50 -0700
- Subject: Re: [testsuite] (checked in) fix gcc.dg/vect/vect-dv-2.c
- References: <20050519231616.GA8566@us.ibm.com> <040d01c55cd8$f2da47d0$2c452597@bagio>
On Fri, May 20, 2005 at 03:12:10AM +0200, Giovanni Bajo wrote:
> Janis Johnson <janis187@us.ibm.com> wrote:
>
> > Auto-vectorization tests should never specify "dg-do run". The
> > default action is "run" if the test hardware supports vector
> > instructions, "compile" otherwise. This gets rid of a failure when
> > the test is run on a PowerPC system without VMX hardware. I'm
> > checking it in on mainline.
>
>
> Since you're at it, I noticed today that there are still two tests in
> gcc.dg/vect which uses dg-do run instead of a specific effective target
> keyword:
>
> vect-82.c:/* { dg-do run { target powerpc*-*-* } } */
> vect-82_64.c:/* { dg-do run { target { powerpc*-*-* && lp64 } } } */
> vect-83.c:/* { dg-do run { target powerpc*-*-* } } */
> vect-83_64.c:/* { dg-do run { target { powerpc*-*-* && lp64 } } } */
I guess I should have said "auto-vectorization tests should never
specify 'dg-do run' unless they call check_vect before executing any
vector code". These could be changed now to use dg-skip-if with an
appropriate selector expression, but they're OK as they are.
Janis