[Bug ld/22751] LTO broken for libgcc libcalls

2018-03-31 Thread jeremip11 at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22751 Jeremi changed: What|Removed |Added CC||jeremip11 at gmail dot com -- You are

[Bug ld/22751] LTO broken for libgcc libcalls

2018-01-27 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22751 Alan Modra changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug ld/22751] LTO broken for libgcc libcalls

2018-01-27 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=22751 --- Comment #7 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by H.J. Lu : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=fef75122c0fe3abafb99d79a63545c1531f4107c commit

[Bug ld/22751] LTO broken for libgcc libcalls

2018-01-27 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=22751 --- Comment #6 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d580dcc7aac21dc8396e8e90ea6d05ec32d6cbb9 commit

[Bug ld/22751] LTO broken for libgcc libcalls

2018-01-27 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=22751 --- Comment #5 from cvs-commit at gcc dot gnu.org --- The binutils-2_30-branch branch has been updated by Nick Clifton :

[Bug ld/22751] LTO broken for libgcc libcalls

2018-01-27 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22751 --- Comment #4 from Alan Modra --- Sigh, so it seems reverting the patch does fix the problem. I don't know what happened when I attempted the revert earlier today.. Now that I've had a bit more time to look at the problem, it seems the

[Bug ld/22751] LTO broken for libgcc libcalls

2018-01-26 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22751 --- Comment #3 from Alan Modra --- Reverting 1fa4ec6ae7 makes no difference. Indeed, now that I've refreshed my memory on what that patch does, it should not since all it is doing (or at least supposed to be doing!) is reordering the layout

[Bug ld/22751] LTO broken for libgcc libcalls

2018-01-26 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22751 H.J. Lu changed: What|Removed |Added CC||hjl.tools at gmail dot com -- You are

[Bug ld/22751] LTO broken for libgcc libcalls

2018-01-26 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22751 Alan Modra changed: What|Removed |Added Status|NEW |ASSIGNED CC|amodra at

[Bug ld/22751] LTO broken for libgcc libcalls

2018-01-26 Thread doko at debian dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=22751 Matthias Klose changed: What|Removed |Added CC||doko at debian dot org -- You are

[Bug ld/22751] LTO broken for libgcc libcalls

2018-01-26 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22751 H.J. Lu changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|