public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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: Sat, 28 Dec 2013 12:33:00 -0000	[thread overview]
Message-ID: <bug-59543-4-nmBLlbTt2Z@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 #4 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
Created attachment 31527
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31527&action=edit
testcase

Here's a small testcase:

  % cat check.sh
g++ -g -fprofile-use -fPIC -flto -fno-exceptions -O2 -std=c++11 -c uniset.ii
g++ -fPIC -flto -fno-exceptions -O2 -std=c++11 -c unistr.ii
g++ -fPIC -flto -fno-exceptions -O2 -std=c++11 -c unorm.ii
gcc -O3 -c -fPIC unorm_it.i
g++ -flto -O2 uniset.o unistr.o unorm_it.o unorm.o
  % ./check.sh
In member function ‘extractBetween’:
lto1: fatal error: Cgraph edge statement index out of range 25 < 50
compilation terminated.
>From gcc-bugs-return-438640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 28 13:30:20 2013
Return-Path: <gcc-bugs-return-438640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25185 invoked by alias); 28 Dec 2013 13:30:19 -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
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25122 invoked by uid 48); 28 Dec 2013 13:30:14 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59612] iso_fortran_env segfaults with -fdump-fortran-original
Date: Sat, 28 Dec 2013 13:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus 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-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-59612-4-silBZAcSNo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59612-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59612-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/msg02295.txt.bz2
Content-length: 1052

http://gcc.gnu.org/bugzilla/show_bug.cgi?idY612

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-valid-code
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-12-28
                 CC|                            |janus at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from janus at gcc dot gnu.org ---
Straightforward patch:

Index: gcc/fortran/dump-parse-tree.c
==================================================================--- gcc/fortran/dump-parse-tree.c    (revision 206176)
+++ gcc/fortran/dump-parse-tree.c    (working copy)
@@ -110,7 +110,8 @@ show_typespec (gfc_typespec *ts)
       break;

     case BT_CHARACTER:
-      show_expr (ts->u.cl->length);
+      if (ts->u.cl)
+    show_expr (ts->u.cl->length);
       fprintf(dumpfile, " %d", ts->kind);
       break;


  parent reply	other threads:[~2013-12-28 12:33 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 [this message]
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
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-nmBLlbTt2Z@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).