public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sfilippone at uniroma2 dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/42274] New: ICE: segmentation fault
Date: Fri, 04 Dec 2009 14:30:00 -0000 [thread overview]
Message-ID: <bug-42274-9410@http.gcc.gnu.org/bugzilla/> (raw)
The attached code gives an ICE against the fortran-dev branch as of r154975.
[sfilippo@donald bug12]$ gfortran -v
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/usr/local/gnudev/libexec/gcc/x86_64-unknown-linux-gnu/4.5.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../fortran-dev/configure --prefix=/usr/local/gnudev
--enable-languages=c,c++,fortran : (reconfigured) ../fortran-dev/configure
--prefix=/usr/local/gnudev --enable-languages=c,c++,fortran
Thread model: posix
gcc version 4.5.0 20091203 (experimental) (GCC)
[sfilippo@donald bug12]$ gfortran -c bug12.f03
bug12.f03:229:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
--
Summary: ICE: segmentation fault
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: sfilippone at uniroma2 dot it
GCC build triplet: x86_64-unknown-linux-gnu
GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42274
next reply other threads:[~2009-12-04 14:30 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 14:30 sfilippone at uniroma2 dot it [this message]
2009-12-04 14:31 ` [Bug fortran/42274] " sfilippone at uniroma2 dot it
2009-12-04 14:48 ` rguenth at gcc dot gnu dot org
2009-12-04 14:58 ` dominiq at lps dot ens dot fr
2009-12-04 15:02 ` sfilippone at uniroma2 dot it
2009-12-04 15:57 ` [Bug fortran/42274] [fortran-dev Regression] " burnus at gcc dot gnu dot org
2009-12-04 17:06 ` janus at gcc dot gnu dot org
2009-12-04 19:44 ` janus at gcc dot gnu dot org
2009-12-04 21:38 ` dominiq at lps dot ens dot fr
2009-12-05 11:21 ` janus at gcc dot gnu dot org
2009-12-05 13:31 ` dominiq at lps dot ens dot fr
2009-12-05 15:14 ` janus at gcc dot gnu dot org
2009-12-05 16:41 ` dominiq at lps dot ens dot fr
2009-12-06 13:33 ` pault at gcc dot gnu dot org
2009-12-10 21:21 ` janus at gcc dot gnu dot org
2010-03-02 9:47 ` dominiq at lps dot ens dot fr
2010-04-22 20:59 ` janus at gcc dot gnu dot org
2010-04-25 14:32 ` janus at gcc dot gnu dot org
2010-04-25 14:43 ` janus at gcc dot gnu dot org
2010-04-25 14:57 ` janus at gcc dot gnu dot org
2010-04-25 16:27 ` pault at gcc dot gnu dot org
2010-04-25 16:39 ` dominiq at lps dot ens dot fr
2010-04-25 16:43 ` janus at gcc dot gnu dot org
2010-04-25 17:10 ` janus at gcc dot gnu dot org
2010-04-25 17:16 ` janus at gcc dot gnu dot org
2010-04-25 18:24 ` janus at gcc dot gnu dot org
2010-04-25 18:28 ` paul dot richard dot thomas at gmail dot com
2010-04-25 18:59 ` paul dot richard dot thomas at gmail dot com
2010-04-25 19:17 ` sfilippone at uniroma2 dot it
2010-04-25 19:50 ` janus at gcc dot gnu dot org
2010-04-25 20:17 ` janus at gcc dot gnu dot org
2010-04-25 20:20 ` sfilippone at uniroma2 dot it
2010-04-25 21:44 ` janus at gcc dot gnu dot org
2010-04-25 22:26 ` janus at gcc dot gnu dot org
2010-04-26 8:23 ` dominiq at lps dot ens dot fr
2010-04-26 9:08 ` janus at gcc dot gnu dot org
2010-04-26 10:57 ` pault at gcc dot gnu dot org
2010-04-29 19:12 ` pault 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=bug-42274-9410@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).