| Message ID | Pine.LNX.4.64.1404022007260.10430@digraph.polyomino.org.uk |
|---|---|
| State | New |
| Headers | show |
On Wed, Apr 2, 2014 at 10:09 PM, Joseph S. Myers <joseph@codesourcery.com> wrote: > Two of the tests I noted in > <http://gcc.gnu.org/ml/gcc-patches/2014-04/msg00036.html> did not get > fixed for --with-arch=bdver3 --with-cpu=bdver3 by adding > -mno-prefer-avx128 in fact also show failures for --with-arch=btver2 > --with-tune=btver2, and in that case *are* fixed by adding > -mno-prefer-avx128. Thus, while in those cases there may still be > other tuning issues as noted in > <http://gcc.gnu.org/ml/gcc-patches/2014-04/msg00052.html> (btver2 > doesn't enable the flag in question) I think it *is* correct to use > -mno-prefer-avx128 for these two tests, and this patch adds it. > > Tested x86_64-linux-gnu. OK to commit? > > 2014-04-02 Joseph Myers <joseph@codesourcery.cmo> > > * gcc.target/i386/avx2-vpand-3.c, > gcc.target/i386/avx256-unaligned-load-2.c: Use -mno-prefer-avx128. OK. Thanks, Uros.
Index: gcc/testsuite/gcc.target/i386/avx2-vpand-3.c =================================================================== --- gcc/testsuite/gcc.target/i386/avx2-vpand-3.c (revision 209023) +++ gcc/testsuite/gcc.target/i386/avx2-vpand-3.c (working copy) @@ -1,5 +1,5 @@ /* { dg-do run } */ -/* { dg-options "-mavx2 -O2 -ftree-vectorize -save-temps" } */ +/* { dg-options "-mavx2 -mno-prefer-avx128 -O2 -ftree-vectorize -save-temps" } */ /* { dg-require-effective-target avx2 } */ Index: gcc/testsuite/gcc.target/i386/avx256-unaligned-load-2.c =================================================================== --- gcc/testsuite/gcc.target/i386/avx256-unaligned-load-2.c (revision 209023) +++ gcc/testsuite/gcc.target/i386/avx256-unaligned-load-2.c (working copy) @@ -1,5 +1,5 @@ /* { dg-do compile { target { ! ia32 } } } */ -/* { dg-options "-O3 -dp -mavx -mavx256-split-unaligned-load" } */ +/* { dg-options "-O3 -dp -mavx -mavx256-split-unaligned-load -mno-prefer-avx128" } */ void avx_test (char **cp, char **ep)