public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51991] Wrong error message with variables named "SAVE*"
Date: Wed, 08 Feb 2012 16:15:00 -0000	[thread overview]
Message-ID: <bug-51991-4-v2HNBfdm0C@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51991-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51991

--- Comment #11 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2012-02-08 16:15:20 UTC ---
On Wed, Feb 08, 2012 at 10:38:42AM +0000, bardeau at iram dot fr wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51991
> 
> --- Comment #10 from Sebastien Bardeau <bardeau at iram dot fr> 2012-02-08 10:38:42 UTC ---
> I checked the gfortran trunk revision 183991 and the "bug" does not seem to be
> fixed. I can also add that the DATA*-named variables give also erroneous
> messages.

The patch has not been checked-in.  And, I have no idea
when I'll have time to add it.


  parent reply	other threads:[~2012-02-08 16:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 10:26 [Bug fortran/51991] New: " bardeau at iram dot fr
2012-01-25 11:06 ` [Bug fortran/51991] " burnus at gcc dot gnu.org
2012-01-25 11:17 ` dominiq at lps dot ens.fr
2012-01-25 12:56 ` bardeau at iram dot fr
2012-01-25 13:17 ` dominiq at lps dot ens.fr
2012-01-25 13:32 ` bardeau at iram dot fr
2012-01-25 13:37 ` bardeau at iram dot fr
2012-01-25 14:09 ` dominiq at lps dot ens.fr
2012-01-25 14:11 ` bardeau at iram dot fr
2012-01-25 16:39 ` kargl at gcc dot gnu.org
2012-02-08 10:39 ` bardeau at iram dot fr
2012-02-08 16:15 ` sgk at troutmask dot apl.washington.edu [this message]
2012-02-08 16:23 ` bardeau at iram dot fr

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-51991-4-v2HNBfdm0C@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).