From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-412276-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 21665 invoked by alias); 15 Jan 2013 17:38:48 -0000
Received: (qmail 19855 invoked by uid 48); 15 Jan 2013 17:38:32 -0000
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/55493] [4.8 Regression] LTO always ICEs on i686-mingw32
Date: Tue, 15 Jan 2013 17:38: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: major
X-Bugzilla-Who: ktietz at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.8.0
X-Bugzilla-Changed-Fields: CC
Message-ID: <bug-55493-4-MOIu3tUtDU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55493-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55493-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: 2013-01/txt/msg01395.txt.bz2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55493

Kai Tietz <ktietz at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ktietz at gcc dot gnu.org

--- Comment #4 from Kai Tietz <ktietz at gcc dot gnu.org> 2013-01-15 17:38:31 UTC ---
(In reply to comment #3)
> (In reply to comment #2)
> > Are you sure that you do not somehow pull in LTO objects from older releases?
> 
> Yes, happens even with -nostdlib, even on builds where I'm absolutely sure
> there's no way an old LTO object could sneak in.

I can't reproduce that.  btw how are you doing linker-tests without specifying
object-code and libraries?
Nevertheless I assume that runtime is build with older-version of gcc.  It is a
bit sad that LTO doesn't tell that version is outdated.

I've tested it with gcc version from 15th of January 2012 and it works
flawless.  But I have rebuild my runtime with new version.  That is recommented
to do.

I would suggest to close that bug as WORKSFORME