From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-437970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 21028 invoked by alias); 18 Dec 2013 10:15:22 -0000
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
Received: (qmail 20998 invoked by uid 48); 18 Dec 2013 10:15:17 -0000
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/59543] [4.9 Regression] lto1: fatal error: Cgraph edge statement index out of range
Date: Wed, 18 Dec 2013 10:15: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-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: trippels at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59543-4-MHwWnim3lp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59543-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59543-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-12/txt/msg01625.txt.bz2

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

--- Comment #2 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #1)
> Thank you,
> can you, please, check that the problem appears still after 
> 2013-12-17  Jan Hubicka  <hubicka@ucw.cz>
> 
>         * ipa-utils.h (possible_polymorphic_call_targets): Determine context
> of
>         the call.
>         * gimple-fold.c (gimple_fold_call): Use ipa-devirt to devirtualize.
> 
> this patch makes early passes to use same analysis for devirtualization as
> IPA passes and thus it should prevent from devirtualization to be discovered
> just after early passes but before IPA analysis.  I suspect those can bring
> LTO streaming out of sync. If this is the case, we need to chase away the
> unreachable code removal that should not be placed in between renumbering
> stmts and streaming.

Yes, it still happens after r206042.