public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth 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: Tue, 18 Mar 2014 14:31:00 -0000	[thread overview]
Message-ID: <bug-59543-4-jM8gNW68kB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59543-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think 2) is the issue, so does

Index: lto-streamer-in.c
===================================================================
--- lto-streamer-in.c   (revision 208642)
+++ lto-streamer-in.c   (working copy)
@@ -988,7 +988,7 @@ input_function (tree fn_decl, struct dat
             We can't remove them earlier because this would cause uid
             mismatches in fixups, but we can do it at this point, as
             long as debug stmts don't require fixups.  */
-         if (!MAY_HAVE_DEBUG_STMTS && is_gimple_debug (stmt))
+         if (!MAY_HAVE_DEBUG_STMTS && !flag_wpa && is_gimple_debug (stmt))
            {
              gimple_stmt_iterator gsi = bsi;
              gsi_next (&bsi);

fix it?

Not sure why we output the original function again.


  parent reply	other threads:[~2014-03-18 14:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18  9:04 [Bug lto/59543] New: " trippels at gcc dot gnu.org
2013-12-18 10:15 ` [Bug lto/59543] " trippels at gcc dot gnu.org
2013-12-19 12:53 ` rguenth at gcc dot gnu.org
2013-12-28 10:26 ` trippels at gcc dot gnu.org
2013-12-28 12:33 ` trippels at gcc dot gnu.org
2014-01-16 11:43 ` trippels at gcc dot gnu.org
2014-02-17 15:28 ` jakub at gcc dot gnu.org
2014-03-02 22:35 ` hubicka at gcc dot gnu.org
2014-03-18 14:31 ` rguenth at gcc dot gnu.org [this message]
2014-03-18 14:44 ` rguenth at gcc dot gnu.org
2014-03-19  9:23 ` rguenth at gcc dot gnu.org
2014-03-19  9:25 ` rguenth at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-59543-4-jM8gNW68kB@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).