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: Sat, 12 Mar 2011 09:56:24 +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 #4 from Iain Sandoe <iains at gcc dot gnu.org> 2011-03-12 09:56:07 UTC ---
confirmed that:
(a) we create too many sections for the gcc.dg/torture/builtin-attr-1.c
testcase (598)
(b) that 'as' does not detect this @XCode 3.2.5
looking at the output of otool -l, we have all the sections preserved in the
initial .o files;
I guess this is because 'as' places all the output in one segment and encodes
the seg/sect information manually.
The next question is 'do we ever present too many sections to the final (post
LTO) link?'
(and, if so, why?)
[it might be that we can live with excess sections in the intermediate objects
(the extras are all in GNU_LTO) - so long as those are removed before we try to
carry out the final link].