This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/48086] bootstrap-lto creates c-common.s with too many sections on x86_64-apple-darwin10
- From: "iains at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 13 Mar 2011 20:54:13 +0000
- Subject: [Bug lto/48086] bootstrap-lto creates c-common.s with too many sections on x86_64-apple-darwin10
- Auto-submitted: auto-generated
- References: <bug-48086-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48086
--- Comment #14 from Iain Sandoe <iains at gcc dot gnu.org> 2011-03-13 20:54:03 UTC ---
(In reply to comment #13)
> Alright, multiple segments will not work. Or even if they do, it is another
> solution that may or may not work in the future depending on the whims of
> Apple.
>
> So, a rewrite it will have to be, then.
the response from Nick is a confirmation of both points:
"The suggestion of using different segment names will not work. Segments
aren't really used in mach-o object files. All mach-o object files have
exactly one LC_SEGMENT load command. It is final linked images that support
multiple LC_SEGMENT load commands.
It is possible to fix this in Xcode 4.x, but I think a solution that just uses
one section for all gcc LTO data (and have your own sub-section scheme) will
work with all darwin assembler versions."
==
I can only hope that the simple_object interface in libiberty will make this
possible without introducing a dependency on libelf (which seems a little OTT
for this relatively small requirement).