[Bug bootstrap/87252] gcc-4.4 cross-builds broken, apparently in self-tests

2020-04-21 Thread hp at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87252 --- Comment #11 from Hans-Peter Nilsson --- (In reply to Hans-Peter Nilsson from comment #0) > (Note: no cross-binutils or anything needed, just gcc sources and a native > gcc-4.4. This is an *old* installation which identifies itself as "gcc >

[Bug bootstrap/87252] gcc-4.4 cross-builds broken, apparently in self-tests

2020-04-10 Thread hp at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87252 --- Comment #10 from Hans-Peter Nilsson --- (In reply to Abrahm Scully from comment #9) > Either way, building gcc-4.7.4 first and then building gcc-10 with that > produces a compiler without the problem. > > Again, sorry for the noise.

[Bug bootstrap/87252] gcc-4.4 cross-builds broken, apparently in self-tests

2020-04-10 Thread abrahm.scully at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87252 --- Comment #9 from Abrahm Scully --- I'm no longer convinced that I didn't see the problem previously because I just wasn't running the tests. Stage 1 has checking enabled... so I don't know why this problem showed up for others in gcc 9 but

[Bug bootstrap/87252] gcc-4.4 cross-builds broken, apparently in self-tests

2020-04-05 Thread abrahm.scully at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87252 --- Comment #8 from Abrahm Scully --- I don't think anything is wrong with gcc-10-20200329. The code looks fine. I realized later that the versions of gcc I mentioned where I don't see this problem are all from release branches. As described in

[Bug bootstrap/87252] gcc-4.4 cross-builds broken, apparently in self-tests

2020-04-05 Thread abrahm.scully at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87252 --- Comment #7 from Abrahm Scully --- I hit an ICE today that looks like this bug. I attempted to build gcc-10-20200329 on 32-bit CentOS 6 using g++ 4.4.7-23.el6. I don't see this bug building gcc-6.3, gcc-7.3, gcc-8.3, or gcc-9-20200118 on the

[Bug bootstrap/87252] gcc-4.4 cross-builds broken, apparently in self-tests

2018-09-07 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87252 --- Comment #6 from David Malcolm --- ...though my understanding is that an automatic local's storage is deallocated at the end of the enclosing code block - presumably that's when the dtor is meant to run, and not before.

[Bug bootstrap/87252] gcc-4.4 cross-builds broken, apparently in self-tests

2018-09-07 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87252 --- Comment #5 from David Malcolm --- Possibly due to lifetime issues: perhaps the on-stack text_range_label's dtor is being called (and thus trashing updating the vtable ptr) before the object gets used. (see e.g.

[Bug bootstrap/87252] gcc-4.4 cross-builds broken, apparently in self-tests

2018-09-07 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87252 --- Comment #4 from David Malcolm --- Looks like it's crashing on a virtual function call, within the code I added in r263564. It says "pure virtual method called", but it's calling it on an instance of text_range_label (on the stack), which

[Bug bootstrap/87252] gcc-4.4 cross-builds broken, apparently in self-tests

2018-09-07 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87252 --- Comment #3 from Andrew Pinski --- Maybe related to PR 87134. There might be more of these issues floating in GCC code where GCC 4.4 does not implement the C++11 sematics of initializing.

[Bug bootstrap/87252] gcc-4.4 cross-builds broken, apparently in self-tests

2018-09-07 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87252 --- Comment #2 from Andrew Pinski --- Should have been fixed via https://gcc.gnu.org/ml/gcc-patches/2018-08/msg01996.html .

[Bug bootstrap/87252] gcc-4.4 cross-builds broken, apparently in self-tests

2018-09-07 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87252 --- Comment #1 from Andrew Pinski --- https://gcc.gnu.org/ml/gcc-patches/2018-08/msg01891.html