public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lei at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/13811] New: -fdump-tree-all causes ICE at tree-inline.c:648 Date: Thu, 22 Jan 2004 09:18:00 -0000 [thread overview] Message-ID: <20040122091815.13811.lei@il.ibm.com> (raw) % cat hello.f90 SUBROUTINE FOO11(A) CHARACTER*11 A A = "HELLO WORLD" END SUBROUTINE FOO11 % gfortran -fdump-tree-all -c hello.f90 hello.f90: In function `foo11': hello.f90:0: internal compiler error: in copy_body_r, at tree-inline.c:648 -- Summary: -fdump-tree-all causes ICE at tree-inline.c:648 Product: gcc Version: tree-ssa Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: lei at il dot ibm dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13811
next reply other threads:[~2004-01-22 9:18 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-22 9:18 lei at il dot ibm dot com [this message] 2004-01-22 9:25 ` [Bug middle-end/13811] " pinskia at gcc dot gnu dot org 2004-01-24 21:22 ` dhazeghi at yahoo dot com 2004-02-08 6:57 ` [Bug middle-end/13811] [gfortran/tree-ssa] " pinskia at gcc dot gnu dot org 2004-04-05 0:01 ` [Bug fortran/13811] " pinskia at gcc dot gnu dot 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=20040122091815.13811.lei@il.ibm.com \ --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: linkBe 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).