public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/29537] ICE in gfc_match_common
Date: Sat, 21 Oct 2006 22:04:00 -0000 [thread overview]
Message-ID: <20061021220424.17163.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29537-11811@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from kargl at gcc dot gnu dot org 2006-10-21 22:04 -------
First, I agree there is a bug because gfortran should not have an
ICE. However, I believe the code is invalid. The Fortran 95
standard specifically mentions "named common blocks" in the
description of "block data". "common c" is a blank common block.
--
kargl at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29537
next prev parent reply other threads:[~2006-10-21 22:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 17:32 [Bug fortran/29537] New: " aldot at gcc dot gnu dot org
2006-10-21 17:42 ` [Bug fortran/29537] " aldot at gcc dot gnu dot org
2006-10-21 18:04 ` aldot at gcc dot gnu dot org
2006-10-21 18:05 ` aldot at gcc dot gnu dot org
2006-10-21 18:49 ` aldot at gcc dot gnu dot org
2006-10-21 18:57 ` pinskia at gcc dot gnu dot org
2006-10-21 22:04 ` kargl at gcc dot gnu dot org [this message]
2006-10-22 11:36 ` [Bug fortran/29537] ICE in gfc_match_common for blank common in BLOCK DATA unit aldot at gcc dot gnu dot org
2006-10-22 11:50 ` aldot at gcc dot gnu dot org
2006-10-22 15:00 ` sgk at troutmask dot apl dot washington dot edu
2006-10-22 21:08 ` aldot at gcc dot gnu dot org
2006-10-26 12:59 ` aldot at gcc dot gnu dot org
2006-10-28 23:56 ` sgk at troutmask dot apl dot washington dot edu
2006-10-31 23:39 ` aldot at gcc dot gnu dot org
2006-10-31 23:42 ` aldot at gcc dot gnu dot org
2006-10-31 23:47 ` sgk at troutmask dot apl dot washington dot edu
2006-11-01 19:30 ` aldot at gcc dot gnu dot org
2006-11-30 19:26 ` chaoyingfu 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=20061021220424.17163.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).