public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "peter.tromso at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51966] New: internal compiler error
Date: Mon, 23 Jan 2012 14:08:00 -0000 [thread overview]
Message-ID: <bug-51966-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51966
Bug #: 51966
Summary: internal compiler error
Classification: Unclassified
Product: gcc
Version: 4.6.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: peter.tromso@gmail.com
Created attachment 26429
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26429
fortran module part of a larger code
Error message (see complete below):
Compiler_error_example.f90:99:0: internal compiler error: in
gfc_conv_array_constructor_expr, at fortran/trans-expr.c:4126
Small example code which triggers the error is attached.(It is extracted from a
much larger code).
Output from compiler:
$ gfortran -v -save-temps -fdefault-real-8 -ffree-line-length-0 -O2 -c
Compiler_error_example.f90
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/global/home/install/gcc/4.6.2/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.6.2/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc-4.6.2/configure --prefix=/global/apps/gcc/4.6.2
Thread model: posix
gcc version 4.6.2 (GCC)
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-fdefault-real-8'
'-ffree-line-length-0' '-O2' '-c' '-mtune=generic' '-march=x86-64'
/global/home/install/gcc/4.6.2/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.6.2/f951
Compiler_error_example.f90 -quiet -dumpbase Compiler_error_example.f90
-mtune=generic -march=x86-64 -auxbase Compiler_error_example -O2 -version
-fdefault-real-8 -ffree-line-length-0 -fintrinsic-modules-path
/global/home/install/gcc/4.6.2/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.6.2/finclude
-o Compiler_error_example.s
GNU Fortran (GCC) version 4.6.2 (x86_64-unknown-linux-gnu)
compiled by GNU C version 4.6.2, GMP version 4.3.2, MPFR version 2.4.2, MPC
version 0.8.1
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU Fortran (GCC) version 4.6.2 (x86_64-unknown-linux-gnu)
compiled by GNU C version 4.6.2, GMP version 4.3.2, MPFR version 2.4.2, MPC
version 0.8.1
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler_error_example.f90: In function 'init_ecosystems':
Compiler_error_example.f90:99:0: internal compiler error: in
gfc_conv_array_constructor_expr, at fortran/trans-expr.c:4126
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
next reply other threads:[~2012-01-23 13:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 14:08 peter.tromso at gmail dot com [this message]
2012-01-23 15:02 ` [Bug fortran/51966] " peter.tromso at gmail dot com
2012-01-23 15:19 ` [Bug fortran/51966] [4.6/4.7 Regression] ICE in gfc_conv_array_constructor_expr burnus at gcc dot gnu.org
2012-01-23 15:21 ` dominiq at lps dot ens.fr
2012-01-23 16:53 ` jakub at gcc dot gnu.org
2012-01-24 10:13 ` burnus at gcc dot gnu.org
2012-01-24 10:20 ` burnus at gcc dot gnu.org
2012-01-25 8:39 ` burnus at gcc dot gnu.org
2012-01-25 8:50 ` burnus at gcc dot gnu.org
2012-01-25 8:53 ` burnus 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-51966-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).