[Bug target/81158] [8 regression] Many test case failures starting with r249424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81158 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Jakub Jelinek --- .
[Bug target/81158] [8 regression] Many test case failures starting with r249424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81158 --- Comment #5 from Bill Schmidt --- That would make sense. I think this can be closed.
[Bug target/81158] [8 regression] Many test case failures starting with r249424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81158 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #4 from Jakub Jelinek --- I don't see these in the current gcc-testresults. Judging from gcc-testresults, has this been fixed with r250295 ?
[Bug target/81158] [8 regression] Many test case failures starting with r249424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81158 --- Comment #3 from seurer at gcc dot gnu.org --- I tried 249423 and don't see those failures but do with 249424. For example: seurer@genoa:~/gcc/build/gcc-test$ updategcc 249423 seurer@genoa:~/gcc/build/gcc-test$ make -j50 seurer@genoa:~/gcc/build/gcc-test$ make -k check-gcc RUNTESTFLAGS=execute.exp=gcc.c-torture/execute/pr51581-1.c 2>&1 > make.249423.out seurer@genoa:~/gcc/build/gcc-test$ grep FAIL make.249423.out seurer@genoa:~/gcc/build/gcc-test$ seurer@genoa:~/gcc/build/gcc-test$ updategcc 249424 seurer@genoa:~/gcc/build/gcc-test$ make -j50 seurer@genoa:~/gcc/build/gcc-test$ make -k check-gcc RUNTESTFLAGS=execute.exp=gcc.c-torture/execute/pr51581-1.c 2>&1 > make.249424.out seurer@genoa:~/gcc/build/gcc-test$ grep FAIL make.249424.out FAIL: gcc.c-torture/execute/pr51581-1.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test FAIL: gcc.c-torture/execute/pr51581-1.c -O3 -g execution test
[Bug target/81158] [8 regression] Many test case failures starting with r249424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81158 --- Comment #2 from Carl Love --- On Thu, 2017-06-22 at 21:06 +, wschmidt at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81158 > > --- Comment #1 from Bill Schmidt --- > I expect this is probably due to the changes to rs6000_gimple_fold_builtin. > Bill: FAIL: gcc.target/powerpc/builtins-3.c scan-assembler-times vmulesh 1 FAIL: gcc.target/powerpc/builtins-3.c scan-assembler-times vmuleuh 1 FAIL: gcc.target/powerpc/builtins-3.c scan-assembler-times vmulosh 1 FAIL: gcc.target/powerpc/builtins-3.c scan-assembler-times vmulouh 1 Unfortunately, this is due to my screw up. The patch to fix the vec_mule and vec_mulo was missing the test case update. I made the change to the test case but didn't get it included in the patch. I have since fixed the above failures, commit 249572. The commit was tested on Power 8 BE, LE and Power 7 to make sure they are all working now. The other tests listed, gcc.c-torture/execute/* and gcc.dg/vect/* I have never touched so I don't think I am responsible for those. :-) Carl
[Bug target/81158] [8 regression] Many test case failures starting with r249424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81158 --- Comment #1 from Bill Schmidt --- I expect this is probably due to the changes to rs6000_gimple_fold_builtin.
[Bug target/81158] [8 regression] Many test case failures starting with r249424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81158 Richard Biener changed: What|Removed |Added Keywords||wrong-code Target||powerpc* Target Milestone|--- |8.0
