[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/22751] LTO broken for libgcc libcalls
From: |
amodra at gmail dot com |
Subject: |
[Bug ld/22751] LTO broken for libgcc libcalls |
Date: |
Sat, 27 Jan 2018 04:10:47 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=22751
--- Comment #3 from Alan Modra <amodra at gmail dot com> ---
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 of object files. Opening
objects, adding their symbols and deciding whether they need including happens
before ld gets to the new 1fa4ec6ae7 code..
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug ld/22751] New: LTO broken for libgcc libcalls, jcowgill+sourceware at jcowgill dot uk, 2018/01/26
- [Bug ld/22751] LTO broken for libgcc libcalls, hjl.tools at gmail dot com, 2018/01/26
- [Bug ld/22751] LTO broken for libgcc libcalls, doko at debian dot org, 2018/01/26
- [Bug ld/22751] LTO broken for libgcc libcalls, amodra at gmail dot com, 2018/01/26
- [Bug ld/22751] LTO broken for libgcc libcalls, hjl.tools at gmail dot com, 2018/01/26
- [Bug ld/22751] LTO broken for libgcc libcalls,
amodra at gmail dot com <=
- [Bug ld/22751] LTO broken for libgcc libcalls, amodra at gmail dot com, 2018/01/27
- [Bug ld/22751] LTO broken for libgcc libcalls, cvs-commit at gcc dot gnu.org, 2018/01/27
- [Bug ld/22751] LTO broken for libgcc libcalls, cvs-commit at gcc dot gnu.org, 2018/01/27
- [Bug ld/22751] LTO broken for libgcc libcalls, cvs-commit at gcc dot gnu.org, 2018/01/27
- [Bug ld/22751] LTO broken for libgcc libcalls, amodra at gmail dot com, 2018/01/27