From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12608 invoked by alias); 12 Feb 2011 17:48:53 -0000 Received: (qmail 12598 invoked by uid 22791); 12 Feb 2011 17:48:53 -0000 X-SWARE-Spam-Status: No, hits=-2.7 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; Sat, 12 Feb 2011 17:48:49 +0000 From: "davek at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/47527] [4.6 regression] -flto -flto-partition=none broken for arm-linux-gnueabi 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: davek at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.6.0 X-Bugzilla-Changed-Fields: Status CC Resolution Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Sat, 12 Feb 2011 18:19:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-02/txt/msg01530.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47527 Dave Korn changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED CC| |davek at gcc dot gnu.org Resolution| |INVALID --- Comment #4 from Dave Korn 2011-02-12 17:48:46 UTC --- Hi guys, yes, this is definitely a linker bug, what must be happening is that there's some kind of private data not getting copied from the real BFD for the file into the dummy replacement BFD used to hold the linker symbols. I'm working on plugin api fixes right now, I'll take a look at how to fix this. Definitely not a GCC bug, so closing, but I'll come back here to mention the fix once I've posted it.