public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45608] Bogus error about procedure attribute
Date: Thu, 09 Sep 2010 05:35:00 -0000 [thread overview]
Message-ID: <20100909053538.12460.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45608-10743@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from burnus at gcc dot gnu dot org 2010-09-09 05:35 -------
I am not sure how to improve this (internally).
NAG also prints:
f95 hjf.f90
Error: hjf.f90, line 26: Inconsistent usage of CURVE
detected at )@%
Error: hjf.f90, line 26: Component of function reference
detected at )@%
However, the error location could be better - instead of pointing to the
NAMELIST line, one could - as NAG, ifort and g95 do - point to the PRINT line,
e.g. g95:
print *, curve(1)%symbol%typee
1
Error: PROCEDURE attribute conflicts with NAMELIST attribute in 'curve' at (1)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45608
next prev parent reply other threads:[~2010-09-09 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 4:39 [Bug fortran/45608] New: " jvdelisle at gcc dot gnu dot org
2010-09-09 5:35 ` burnus at gcc dot gnu dot org [this message]
[not found] <bug-45608-4@http.gcc.gnu.org/bugzilla/>
2013-06-15 13:16 ` [Bug fortran/45608] " dominiq at lps dot ens.fr
2015-02-01 13:14 ` jvdelisle at gcc dot gnu.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=20100909053538.12460.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).