This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/49992] lto-bootstrap reveals duplicate symbols on x86_64-apple-darwin11
- From: "mrs at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 31 Aug 2011 17:48:05 +0000
- Subject: [Bug target/49992] lto-bootstrap reveals duplicate symbols on x86_64-apple-darwin11
- Auto-submitted: auto-generated
- References: <bug-49992-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49992
--- Comment #51 from mrs at gcc dot gnu.org <mrs at gcc dot gnu.org> 2011-08-31 17:48:05 UTC ---
So, I propose we fix this now and deal with any potential fallout later.
Slightly bug pushing, which I'm not terribly fond of, but, better than leaving
it sit. The other fix, arguable better, would be to never use a public common
for this lto data. I don't understand and know lto well enough to know what to
suggest. If things can look at private symbols, maybe make it private. If it
doesn't have to be storage, make it an absolute value. Add a target hook to
generate it, and then do something special for darwin. Make it a hard define,
which is weak. Try one's hand at COMDAT on it. When it comes to shared
libraries, having any trace of common could be a deal killer anyway.