public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bardeau at iram dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/51991] New: Wrong error message with variables named "SAVE*" Date: Wed, 25 Jan 2012 10:26:00 -0000 [thread overview] Message-ID: <bug-51991-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51991 Bug #: 51991 Summary: Wrong error message with variables named "SAVE*" Classification: Unclassified Product: gcc Version: fortran-dev Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: bardeau@iram.fr Created attachment 26455 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26455 This file raises an error, but with wrong message Hello, in the attached you will find a subroutine which raises an error (on purpose). While one expect the following message: gfortran-error.f90:11.11: savej = a%j 1 Error: 'j' at (1) is not a member of the 'mytyp' structure gfortran (4.7.0 20111119) raises: gfortran-error.f90:11.9: savej = a%j 1 Error: Syntax error in SAVE statement at (1)
next reply other threads:[~2012-01-25 10:06 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-25 10:26 bardeau at iram dot fr [this message] 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 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@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: linkBe 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).