public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57042] New: ICE/Segfault with -fdump-parse-tree
Date: Tue, 23 Apr 2013 10:09:00 -0000	[thread overview]
Message-ID: <bug-57042-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 57042
           Summary: ICE/Segfault with -fdump-parse-tree
    Classification: Unclassified
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: burnus@gcc.gnu.org


use iso_fortran_env; print *, real_kinds ; end

fails with:
f951: internal compiler error: Segmentation fault
0x9a43af crash_signal
        ../../gcc/toplev.c:332
0x56e974 show_typespec
        ../../gcc/fortran/dump-parse-tree.c:113


             reply	other threads:[~2013-04-23 10:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 10:09 burnus at gcc dot gnu.org [this message]
2013-05-01 18:49 ` [Bug fortran/57042] " tkoenig at gcc dot gnu.org
2013-05-01 18:54 ` dominiq at lps dot ens.fr
2013-05-01 19:08 ` [Bug fortran/57042] [4.7/4.8/4.9 Regression] " dominiq at lps dot ens.fr
2013-05-01 19:45 ` tkoenig at gcc dot gnu.org
2013-05-15 13:28 ` rguenth at gcc dot gnu.org
2013-12-31 14:58 ` [Bug fortran/57042] [4.7/4.8 " janus at gcc dot gnu.org
2013-12-31 15:05 ` janus at gcc dot gnu.org
2014-01-09 11:06 ` janus at gcc dot gnu.org
2014-01-11 11:54 ` janus at gcc dot gnu.org
2014-01-11 20:35 ` janus at gcc dot gnu.org
2014-01-11 22:48 ` janus at gcc dot gnu.org
2014-01-11 23:03 ` [Bug fortran/57042] " janus at gcc dot gnu.org
2014-06-12 13:53 ` rguenth at gcc dot gnu.org
2021-12-29 13:37 ` [Bug fortran/57042] Strange typespec " fxcoudert 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-57042-4@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).