[Bug ipa/63814] g++.dg/ipa/pr61160-1.C fails with -m32 on darwin14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63814 --- Comment #12 from Igor Zamyatin izamyatin at gmail dot com --- So far it seems the issue unlikely caused by PIC-related changes in i686 - test passes with -fno-devirtualize.
[Bug ipa/63814] g++.dg/ipa/pr61160-1.C fails with -m32 on darwin14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63814 --- Comment #13 from H.J. Lu hjl.tools at gmail dot com --- (In reply to Igor Zamyatin from comment #11) Will take a look. Thanks! On Linux, the 32-bit PIC regression was introduced by r202145.
[Bug ipa/63814] g++.dg/ipa/pr61160-1.C fails with -m32 on darwin14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63814 --- Comment #14 from H.J. Lu hjl.tools at gmail dot com --- (In reply to H.J. Lu from comment #13) (In reply to Igor Zamyatin from comment #11) Will take a look. Thanks! On Linux, the 32-bit PIC regression was introduced by r202145. It is a -fdevirtualize-speculatively bug.
[Bug ipa/63814] g++.dg/ipa/pr61160-1.C fails with -m32 on darwin14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63814 --- Comment #10 from Uroš Bizjak ubizjak at gmail dot com --- (In reply to Uroš Bizjak from comment #9) (In reply to Igor Zamyatin from comment #7) So, is this compile time failure or runtime failure (or both for two tests)? You can run the testsuite with -m32 -fpic on linux using: make -j 4 -k check RUNTESTFLAGS=--target_board=unix/-m32/-fpic I see: FAIL: g++.dg/ipa/pr61160-2.C -std=gnu++98 execution test FAIL: g++.dg/ipa/pr61160-2.C -std=gnu++11 execution test FAIL: g++.dg/ipa/pr61160-2.C -std=gnu++14 execution test with the above command on i686-linux-gnu.
[Bug ipa/63814] g++.dg/ipa/pr61160-1.C fails with -m32 on darwin14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63814 --- Comment #11 from Igor Zamyatin izamyatin at gmail dot com --- Will take a look. Thanks!
[Bug ipa/63814] g++.dg/ipa/pr61160-1.C fails with -m32 on darwin14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63814 --- Comment #4 from Martin Jambor jamborm at gcc dot gnu.org --- Dominique, if you could pinpoint exactly the revision causing this, it would be great. Most of us do not have access to a darwin machine. Thanks.
[Bug ipa/63814] g++.dg/ipa/pr61160-1.C fails with -m32 on darwin14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63814 --- Comment #5 from Dominique d'Humieres dominiq at lps dot ens.fr --- Dominique, if you could pinpoint exactly the revision causing this, it would be great. Most of us do not have access to a darwin machine. Thanks. It was what I tried to do, but I finally found that the failures do not trigger when gcc is configured with --enable-checking=release (probably obvious). This appeared between revisions r216154 (OK) and r216633 (ICE). Then this should be replaced with This appeared between revisions r216102 (OK) and r216633 (ICE). I'll restart the bisection without --enable-checking=release!-( Note that I have found the following problem [Book15] f90/bug% /opt/gcc/gcc4.10p-216154p2b/bin/g++ -O3 --param ipa-cp-eval-threshold=1 /opt/gcc/work/gcc/testsuite/g++.dg/ipa/pr61160-2.C -std=gnu++11 -m32 -std=gnu++98 [Book15] f90/bug% a.out Abort where 216154p2b is r216154 with patches to bootstrap.
[Bug ipa/63814] g++.dg/ipa/pr61160-1.C fails with -m32 on darwin14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63814 Dominique d'Humieres dominiq at lps dot ens.fr changed: What|Removed |Added CC||kyukhin at gcc dot gnu.org --- Comment #6 from Dominique d'Humieres dominiq at lps dot ens.fr --- These regressions are due to pr216154 and do not show when gcc is configured with --enable-checking=release.
[Bug ipa/63814] g++.dg/ipa/pr61160-1.C fails with -m32 on darwin14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63814 Igor Zamyatin izamyatin at gmail dot com changed: What|Removed |Added CC||evstupac at gmail dot com, ||izamyatin at gmail dot com --- Comment #7 from Igor Zamyatin izamyatin at gmail dot com --- So, is this compile time failure or runtime failure (or both for two tests)?
[Bug ipa/63814] g++.dg/ipa/pr61160-1.C fails with -m32 on darwin14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63814 --- Comment #8 from Dominique d'Humieres dominiq at lps dot ens.fr --- So, is this compile time failure or runtime failure (or both for two tests)? If gcc is configured without --enable-checking=release (default checking for trunk), it is a compile problem. If gcc is configured with --enable-checking=release, it is a runtime problem.
[Bug ipa/63814] g++.dg/ipa/pr61160-1.C fails with -m32 on darwin14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63814 --- Comment #9 from Uroš Bizjak ubizjak at gmail dot com --- (In reply to Igor Zamyatin from comment #7) So, is this compile time failure or runtime failure (or both for two tests)? You can run the testsuite with -m32 -fpic on linux using: make -j 4 -k check RUNTESTFLAGS=--target_board=unix/-m32/-fpic
[Bug ipa/63814] g++.dg/ipa/pr61160-1.C fails with -m32 on darwin14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63814 Francois-Xavier Coudert fxcoudert at gcc dot gnu.org changed: What|Removed |Added Target||x86_64-apple-darwin14 Status|UNCONFIRMED |NEW Last reconfirmed||2014-11-11 CC||enkovich.gnu at gmail dot com, ||marxin at gcc dot gnu.org Host||x86_64-apple-darwin14 Ever confirmed|0 |1 Build||x86_64-apple-darwin14
[Bug ipa/63814] g++.dg/ipa/pr61160-1.C fails with -m32 on darwin14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63814 --- Comment #1 from Dominique d'Humieres dominiq at lps dot ens.fr --- This appeared between revisions r216154 (OK) and r216633 (ICE).
[Bug ipa/63814] g++.dg/ipa/pr61160-1.C fails with -m32 on darwin14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63814 --- Comment #2 from Dominique d'Humieres dominiq at lps dot ens.fr --- r216305 (+patches to bootstrap) is OK.
[Bug ipa/63814] g++.dg/ipa/pr61160-1.C fails with -m32 on darwin14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63814 --- Comment #3 from Dominique d'Humieres dominiq at lps dot ens.fr --- Same failure for g++.dg/ipa/pr61160-2.C.
