On Wed, Sep 10, 2014 at 01:57:01PM +0000, VandeVondele Joost wrote:
> Thanks for testing.
>
> The vect-args.c I explained earlier, and is indeed due to i386.exp hardcoding
> those.
IMHO the best fix for that is following, use the same predicate whether to
run the vect-args.c tests or not as is used for all other tests.
Ok for trunk?
2014-09-10 Jakub Jelinek <ja...@redhat.com>
* gcc.target/i386/i386.exp: Only run vect-args.c tests
if runtest_file_p says they should be run.
--- gcc/testsuite/gcc.target/i386/i386.exp.jj 2014-06-10 07:58:09.000000000
+0200
+++ gcc/testsuite/gcc.target/i386/i386.exp 2014-09-10 16:09:31.572493879
+0200
@@ -316,13 +316,16 @@ if ![info exists DEFAULT_CFLAGS] then {
dg-init
clearcap-init
+global runtests
# Special case compilation of vect-args.c so we don't have to
# replicate it 10 times.
-foreach type { "" -mmmx -m3dnow -msse -msse2 } {
- foreach level { "" -O } {
- set flags "$type $level"
- verbose -log "Testing vect-args, $flags" 1
- dg-test $srcdir/$subdir/vect-args.c $flags ""
+if [runtest_file_p $runtests $srcdir/$subdir/vect-args.c] {
+ foreach type { "" -mmmx -m3dnow -msse -msse2 } {
+ foreach level { "" -O } {
+ set flags "$type $level"
+ verbose -log "Testing vect-args, $flags" 1
+ dg-test $srcdir/$subdir/vect-args.c $flags ""
+ }
}
}
Jakub
