This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Questions about the dg-do directive
- From: dominiq at lps dot ens dot fr (Dominique Dhumieres)
- To: schwab at linux-m68k dot org, janisjo at codesourcery dot com
- Cc: ro at CeBiTec dot Uni-Bielefeld dot DE, mikestump at comcast dot net, janisjo at codesourcery dot com, gcc at gcc dot gnu dot org, dominiq at lps dot ens dot fr
- Date: Wed, 17 Oct 2012 00:31:19 +0200
- Subject: Re: Questions about the dg-do directive
- References: <20121016132011.F157F3BE1C@mailhost.lps.ens.fr> <m2vceay05q.fsf@igel.home> <507D7EA1.90406@mentor.com>
Thanks for the quick answer.
> That's just the way it works, so I suppose you could call it a feature.
So the answer to (1) is yes and to (2) it is a poorly documented feature.
May be the restriction to one dg-do directive should be added to
http://gcc.gnu.org/wiki/HowToPrepareATestcase .
In gcc/testsuite/* I have found 27 instances of such double directives
most of the in the powerpc tests (gcc.target/powerpc/altivec*).
I can provide a list if it helps.
> ... We have much better ways in
> local test directives to skip and xfail tests for different targets.
Could you elaborate please? AFAIU skip or xfail do not allow to do
what was intended in the gcc.target/powerpc/altivec* cases for instance:
run for powerpc*-*-* && vmx_hw and compile for
powerpc*-*-* && { ! vmx_hw }.
Dominique