public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pmason at ricardo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/50163] New: Internal compiler error: initialization expression
Date: Tue, 23 Aug 2011 09:41:00 -0000 [thread overview]
Message-ID: <bug-50163-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50163
Bug #: 50163
Summary: Internal compiler error: initialization expression
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: pmason@ricardo.com
Get following error message when compiling (gfortran -c test.f90):
f951: 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.
Offending source code (test.f90):
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
module stringy
character(len=2) :: xx='aa'
integer :: iloc=index(xx,'bb')
end module stringy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
NOTE: I think the code is slightly illegal - i.e. xx should be compile-time
constant. Compiles OK if xx is qualified as a parameter.
next reply other threads:[~2011-08-23 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 9:41 pmason at ricardo dot com [this message]
2011-08-23 10:21 ` [Bug fortran/50163] " dominiq at lps dot ens.fr
2011-08-23 12:14 ` [Bug fortran/50163] [4.3/4.4/4.5/4.6/4.7 Regression] ICE: " burnus at gcc dot gnu.org
2011-08-24 13:26 ` burnus at gcc dot gnu.org
2011-08-24 14:02 ` jakub at gcc dot gnu.org
2011-08-25 8:33 ` burnus at gcc dot gnu.org
2011-08-30 7:26 ` [Bug fortran/50163] [4.4/4.5 " burnus at gcc dot gnu.org
2011-08-30 12:24 ` [Bug fortran/50163] [4.4/4.5/4.6/4.7 " 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-50163-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).