[Bug bootstrap/80447] Profiled LTO bootstrap fails on powerpc64le

2017-04-19 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447 --- Comment #11 from Martin Sebor --- (In reply to Markus Trippelsdorf from comment #10) > (In reply to Martin Sebor from comment #9) > > > > It's possible that the path is not reachable and GCC doesn't see it. > > Well, 18 exabytes allocations

[Bug bootstrap/80447] Profiled LTO bootstrap fails on powerpc64le

2017-04-18 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447 --- Comment #10 from Markus Trippelsdorf --- (In reply to Martin Sebor from comment #9) > > It's possible that the path is not reachable and GCC doesn't see it. Well, 18 exabytes allocations or memsets would not go unnoticed for very long...

[Bug bootstrap/80447] Profiled LTO bootstrap fails on powerpc64le

2017-04-18 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org --- Comment #9

[Bug bootstrap/80447] Profiled LTO bootstrap fails on powerpc64le

2017-04-17 Thread wschmidt at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447 Bill Schmidt changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug bootstrap/80447] Profiled LTO bootstrap fails on powerpc64le

2017-04-17 Thread wschmidt at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447 Bill Schmidt changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug bootstrap/80447] Profiled LTO bootstrap fails on powerpc64le

2017-04-17 Thread wschmidt at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447 --- Comment #6 from Bill Schmidt --- OK, thanks. I am trying with --disable-werror now, and hopefully that's all there is to it.

[Bug bootstrap/80447] Profiled LTO bootstrap fails on powerpc64le

2017-04-17 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447 --- Comment #5 from Markus Trippelsdorf --- (In reply to Bill Schmidt from comment #4) > (In reply to Markus Trippelsdorf from comment #3) > > I always use --disable-werror to get past these (harmless) warnings. > > Is that harmless, though? 18

[Bug bootstrap/80447] Profiled LTO bootstrap fails on powerpc64le

2017-04-17 Thread wschmidt at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447 --- Comment #4 from Bill Schmidt --- (In reply to Markus Trippelsdorf from comment #3) > I always use --disable-werror to get past these (harmless) warnings. Is that harmless, though? 18446744073709551608 seems like a lot of zeros. :)

[Bug bootstrap/80447] Profiled LTO bootstrap fails on powerpc64le

2017-04-17 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447 Markus Trippelsdorf changed: What|Removed |Added CC||trippels at gcc dot gnu.org --- Co

[Bug bootstrap/80447] Profiled LTO bootstrap fails on powerpc64le

2017-04-17 Thread wschmidt at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447 --- Comment #2 from Bill Schmidt --- Well, not a 7 regression, this is actually an improvement over GCC 6, where we fail during the profile-generate stage...

[Bug bootstrap/80447] Profiled LTO bootstrap fails on powerpc64le

2017-04-17 Thread wschmidt at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447 Bill Schmidt changed: What|Removed |Added Target||powerpc64le-linux-gnu CC|

[Bug bootstrap/80447] Profiled LTO bootstrap fails on powerpc64le

2017-04-17 Thread wschmidt at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447 --- Comment #1 from Bill Schmidt --- Created attachment 41208 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41208&action=edit Configuration log