This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/45375] [meta-bug] Issues with building Mozilla with LTO
- From: "hubicka at ucw dot cz" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 2 Dec 2010 08:47:44 +0000
- Subject: [Bug lto/45375] [meta-bug] Issues with building Mozilla with LTO
- Auto-submitted: auto-generated
- References: <bug-45375-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45375
--- Comment #13 from Jan Hubicka <hubicka at ucw dot cz> 2010-12-02 08:47:28 UTC ---
> Yeh, precisely. The ironly file is a placeholder into which we put the
> symbols found in the lto symtab so that they can take part in the link and
> their resolutions be determined. We have no way of conveying any symbol type
The error comes out after the lto1 invocation, so why the ironly section is
still around?
I would expect it to be discarded at that time and replaced by whatever
compiler
returns to you.
On the other hand, discarding won't help if there was non-LTO module
referencing
TLS var also used by LTO module I guess.