https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80915
H.J. Lu changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80915
--- Comment #4 from H.J. Lu ---
This may be fixed by r248687.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80915
Nathan Sidwell changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80915
--- Comment #3 from Nathan Sidwell ---
Works for me:
/data/users/nathans/trunk/obj/x86_64-lto/./prev-gcc/xg++
-B/data/users/nathans/trunk/obj/x86_64-lto/./prev-gcc/
-B/usr/local/x86_64-pc-linux-gnu/bin/ -nostdinc++
-B/data/users/nathans/trunk/obj
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80915
--- Comment #2 from H.J. Lu ---
(In reply to Nathan Sidwell from comment #1)
> I cannot reproduce this. an x86_64-linux host using
> --with-build-config=bootstrap-lto
>
>
> How exactly is gcc being configured and built? Alternatively, is is
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80915
--- Comment #1 from Nathan Sidwell ---
I cannot reproduce this. an x86_64-linux host using
--with-build-config=bootstrap-lto
How exactly is gcc being configured and built? Alternatively, is is possible
for a self-contained testcase?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80915
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |8.0
