[Bug target/70356] gcc.target/i386/avx-vextractf128-256-5.c FAILs

2016-03-23 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70356 --- Comment #5 from Jakub Jelinek --- I guess we need to wait on Kirill for the reason why the test has been added. It could be that it has been assembled badly, and then dg-do assemble is completely reasonable. Or it could be added for other

[Bug target/70356] gcc.target/i386/avx-vextractf128-256-5.c FAILs

2016-03-23 Thread ro at CeBiTec dot Uni-Bielefeld.DE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70356 --- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #2 from Jakub Jelinek --- > Seems this test is the only one in gcc.target/i386 that has > dg-require-effective-target above dg-do. > Can you please try: > ---

[Bug target/70356] gcc.target/i386/avx-vextractf128-256-5.c FAILs

2016-03-23 Thread ro at CeBiTec dot Uni-Bielefeld.DE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70356 --- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #1 from Jakub Jelinek --- [...] > But, avx-vextractf128-256-5.c has: > dg-require-effective-target avx512f, so wonder what is the problem. > Does the order of dg-do vs.

[Bug target/70356] gcc.target/i386/avx-vextractf128-256-5.c FAILs

2016-03-22 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70356 --- Comment #2 from Jakub Jelinek --- Seems this test is the only one in gcc.target/i386 that has dg-require-effective-target above dg-do. Can you please try: --- gcc/testsuite/gcc.target/i386/avx-vextractf128-256-5.c 2016-01-28

[Bug target/70356] gcc.target/i386/avx-vextractf128-256-5.c FAILs

2016-03-22 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70356 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #1