[Bug testsuite/79273] FAIL: c-c++-common/Wduplicated-branches-13.c -std=gnu++98 (test for excess errors)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79273 Thomas Preud'homme changed: What|Removed |Added Last reconfirmed||2017-1-30 CC||thopre01 at gcc dot gnu.org --- Comment #1 from Thomas Preud'homme --- Also fail for arm-none-eabi targets.
[Bug testsuite/79273] FAIL: c-c++-common/Wduplicated-branches-13.c -std=gnu++98 (test for excess errors)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79273 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|2017-01-30 00:00:00 |2017-02-13 CC||msebor at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #2 from Martin Sebor --- I can't reproduce these failures with an hppa2.0w-hp-hpux11.11 cross-compiler and I don't see them in the most recent test results for the target (https://gcc.gnu.org/ml/gcc-testresults/2017-02/msg01446.html), or on arm-none-linux-gnueabi (https://gcc.gnu.org/ml/gcc-testresults/2017-02/msg01227.html). Is this still an issue or has the problem been fixed?
[Bug testsuite/79273] FAIL: c-c++-common/Wduplicated-branches-13.c -std=gnu++98 (test for excess errors)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79273 John David Anglin changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|--- |FIXED --- Comment #3 from John David Anglin --- I believe this was fixed by the following: 2017-01-27 Jakub Jelinek PR c/79199 * c-c++-common/Wduplicated-branches-13.c: Require int32plus effective target. Use 4294967293U instead of 4294967293.
[Bug testsuite/79273] FAIL: c-c++-common/Wduplicated-branches-13.c -std=gnu++98 (test for excess errors)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79273 --- Comment #4 from Thomas Preud'homme --- (In reply to Martin Sebor from comment #2) > I can't reproduce these failures with an hppa2.0w-hp-hpux11.11 > cross-compiler and I don't see them in the most recent test results for the > target (https://gcc.gnu.org/ml/gcc-testresults/2017-02/msg01446.html), or on > arm-none-linux-gnueabi > (https://gcc.gnu.org/ml/gcc-testresults/2017-02/msg01227.html). Is this > still an issue or has the problem been fixed? It is now passing for arm-none-eabi as well.