[Bug testsuite/80694] [8 regression] test cases gcc.dg/vect/vect-44.c and vect-50.c fail starting with r247780

2017-05-10 Thread wschmidt at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80694 Bill Schmidt changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug testsuite/80694] [8 regression] test cases gcc.dg/vect/vect-44.c and vect-50.c fail starting with r247780

2017-05-10 Thread seurer at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80694 --- Comment #4 from seurer at gcc dot gnu.org --- These tests have flip-flopped between working and not several times recently. I will got back through the logs and run some test to see if I can find where things started to go bad.

[Bug testsuite/80694] [8 regression] test cases gcc.dg/vect/vect-44.c and vect-50.c fail starting with r247780

2017-05-10 Thread wschmidt at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80694 --- Comment #3 from Bill Schmidt --- (In reply to Bill Schmidt from comment #2) > I think probably these tests failed before the fix, stopped failing with the > fix, and started failing again when the fix was reverted. So the revision > number

[Bug testsuite/80694] [8 regression] test cases gcc.dg/vect/vect-44.c and vect-50.c fail starting with r247780

2017-05-10 Thread wschmidt at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80694 --- Comment #2 from Bill Schmidt --- I think probably these tests failed before the fix, stopped failing with the fix, and started failing again when the fix was reverted. So the revision number is a red herring -- we need to figure out when

[Bug testsuite/80694] [8 regression] test cases gcc.dg/vect/vect-44.c and vect-50.c fail starting with r247780

2017-05-10 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80694 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|