From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-380915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 20788 invoked by alias); 23 Jan 2012 10:12:32 -0000
Received: (qmail 20779 invoked by uid 22791); 23 Jan 2012 10:12:31 -0000
X-SWARE-Spam-Status: No, hits=-2.9 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO gcc.gnu.org) (127.0.0.1)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 23 Jan 2012 10:12:18 +0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
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)
Date: Mon, 23 Jan 2012 10:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-51916-4-VGAMouWIP4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51916-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51916-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2012-01/txt/msg02590.txt.bz2

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.