This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/51916] FAIL: gcc.dg/lto/trans-mem-3 c_lto_trans-mem-3_0.o-c_lto_trans-mem-3_1.o link, -flto (internal compiler error)
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 23 Jan 2012 10:11:48 +0000
- Subject: [Bug lto/51916] FAIL: gcc.dg/lto/trans-mem-3 c_lto_trans-mem-3_0.o-c_lto_trans-mem-3_1.o link, -flto (internal compiler error)
- Auto-submitted: auto-generated
- References: <bug-51916-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51916
--- Comment #10 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-23 10:11:48 UTC ---
(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
>
>
> > ... so this is a build/config issue - or, alternatively, the segment name can
> > be specified as above since it is ignored for non-mach-o platforms.
>
> note:
> gcc/lto/lto-object.c
> hardwires this without any ill effect on other platforms. So, since the test
> and the section are lto-specific, I'd suspect that this is the right solution
> rather than some tricky config machinery.
Yes. Can you please post it to gcc-patches@ and commit it? It's preapproved
as obviously correct. Thx.