[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 13:01:41 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=22751
--- Comment #4 from Alan Modra <amodra at gmail dot com> ---
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 patch is
causing _divdi3.o extracted from libgcc.a to not be on the file_chain list.
This is the list used by LANG_FOR_EACH_INPUT_STATEMENT in
output_section_callback, so the .text section from that file is not seen by
map_input_to_output_sections and thus has no output section. Symbols defined
in a section without output section are unresolvable
(elf-bfd.h:RELOC_FOR_GLOBAL_SYMBOL).
--
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, 2018/01/26
- [Bug ld/22751] LTO broken for libgcc libcalls,
amodra at gmail dot com <=
- [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