public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl dot washington dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/27954] ICE on garbage in DATA statement
Date: Mon, 12 Jun 2006 23:07:00 -0000 [thread overview]
Message-ID: <20060612230420.6879.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27954-1771@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from sgk at troutmask dot apl dot washington dot edu 2006-06-12 23:04 -------
Subject: Re: ICE on garbage in DATA statement
On Mon, Jun 12, 2006 at 03:32:15PM -0000, reichelt at gcc dot gnu dot org
wrote:
>----- Comment #4 from reichelt at gcc dot gnu dot org 2006-06-12 15:32 -------
> Maybe it's target dependent?
I'm guessing this is the case.
> Are you using --enable-checking?
I had not checking on i386-*-freebsd and this morning
I rebuilt with --enable-checking on amd64-*-freebsd.
I do not see the Internal Compiler Error.
troutmask:sgk[203] gfc4x -v
Using built-in specs.
Target: amd64-unknown-freebsd7.0
Configured with: ../gcc4x/configure --prefix=/home/sgk/work/4x
--enable-languages=c,fortran --enable-checking
Thread model: posix
gcc version 4.2.0 20060612 (experimental)
troutmask:sgk[204] gfc4x -c l.f90
In file l.f90:3
character*20 X 0
1
Error: Syntax error in data declaration at (1)
In file l.f90:4
data X /'A'/ 0
1
Error: Syntax error in DATA statement at (1)
In file l.f90:4
data X /'A'/ 0
1
Error: Incompatible types in assignment at (1), CHARACTER(1) to REAL(4)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27954
next prev parent reply other threads:[~2006-06-12 23:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 11:00 [Bug fortran/27954] New: " reichelt at gcc dot gnu dot org
2006-06-12 0:14 ` [Bug fortran/27954] " kargl at gcc dot gnu dot org
2006-06-12 12:51 ` reichelt at gcc dot gnu dot org
2006-06-12 14:41 ` kargl at gcc dot gnu dot org
2006-06-12 15:34 ` reichelt at gcc dot gnu dot org
2006-06-12 23:07 ` sgk at troutmask dot apl dot washington dot edu [this message]
2006-06-13 0:10 ` reichelt at gcc dot gnu dot org
2006-06-13 0:56 ` sgk at troutmask dot apl dot washington dot edu
2006-06-13 1:56 ` sgk at troutmask dot apl dot washington dot edu
2006-06-16 2:33 ` reichelt at gcc dot gnu dot org
2006-09-11 1:34 ` jvdelisle at gcc dot gnu dot org
2006-09-11 1:40 ` jvdelisle at gcc dot gnu dot org
2006-10-20 3:24 ` jvdelisle at gcc dot gnu dot org
2006-10-20 3:26 ` jvdelisle at gcc dot gnu dot org
2006-10-20 3:54 ` jvdelisle at gcc dot gnu dot org
2006-10-20 4:50 ` pault at gcc dot gnu dot org
2006-10-20 9:20 ` pault at gcc dot gnu dot org
2006-10-20 14:28 ` jvdelisle at gcc dot gnu dot org
2006-10-20 14:33 ` jvdelisle at gcc dot gnu dot org
2006-10-20 14:35 ` pault at gcc dot gnu dot org
2006-10-20 16:25 ` jvdelisle at gcc dot gnu dot org
2006-10-27 20:47 ` jvdelisle at gcc dot gnu dot org
2006-10-27 20:55 ` jvdelisle at gcc dot gnu dot org
2006-10-27 20:59 ` jvdelisle at gcc dot gnu dot org
2007-02-04 20:11 ` jvdelisle at gcc dot gnu dot org
2007-09-25 10:26 ` jakub 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=20060612230420.6879.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).