public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/31716] segfault with real array bounds
Date: Thu, 26 Apr 2007 21:47:00 -0000 [thread overview]
Message-ID: <20070426214746.9914.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31716-10391@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from tkoenig at gcc dot gnu dot org 2007-04-26 22:47 -------
My analysis in the original bug report wasn't correct.
Here is a shorter version:
$ cat real-dim-2.f90
program main
real :: a(2.0),b(2.0)
a = b
end program main
$ gfortran real-dim-2.f90
real-dim-2.f90:2.12:
real :: a(2.0),b(2.0)
1
Error: Expression at (1) must be of INTEGER type
real-dim-2.f90:2.16:
real :: a(2.0),b(2.0)
1
Error: The module or main program array 'a' at (1) must have constant shape
real-dim-2.f90:2.19:
real :: a(2.0),b(2.0)
1
Error: Expression at (1) must be of INTEGER type
real-dim-2.f90:2.23:
real :: a(2.0),b(2.0)
1
Error: The module or main program array 'b' at (1) must have constant shape
real-dim-2.f90:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
--
tkoenig at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|segfault after mixing |segfault with real array
|declarations and executable |bounds
|statements |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31716
next prev parent reply other threads:[~2007-04-26 21:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 18:50 [Bug fortran/31716] New: segfault after mixing declarations and executable statements tkoenig at gcc dot gnu dot org
2007-04-26 21:47 ` tkoenig at gcc dot gnu dot org [this message]
2007-05-01 13:18 ` [Bug fortran/31716] segfault with real array bounds tkoenig at gcc dot gnu dot org
2007-05-01 13:56 ` jvdelisle at gcc dot gnu dot org
2007-05-02 3:19 ` jvdelisle at gcc dot gnu dot org
2007-05-12 5:03 ` jvdelisle at gcc dot gnu dot org
2007-05-17 19:27 ` dfranke at gcc dot gnu dot org
2007-05-18 2:13 ` jvdelisle at gcc dot gnu dot org
2007-05-18 7:50 ` dfranke at gcc dot gnu dot org
2007-05-18 7:53 ` dfranke at gcc dot gnu dot org
2007-05-18 22:59 ` jvdelisle at gcc dot gnu dot org
2007-05-19 0:30 ` patchapp at dberlin dot org
2007-05-24 5:04 ` jvdelisle at gcc dot gnu dot org
2007-05-24 5:06 ` jvdelisle 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=20070426214746.9914.qmail@sourceware.org \
--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).