public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65751] Bogus &L in error message
Date: Mon, 13 Apr 2015 13:46:00 -0000 [thread overview]
Message-ID: <bug-65751-4-RKprDImnGR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65751-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65751
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-04-13
CC| |pault at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Shouldn't it be rather
@@ -3632,9 +3632,9 @@ gfc_check_pointer_assign (gfc_expr *lval
|| (lvalue->ts.type == BT_DERIVED
&& (lvalue->ts.u.derived->attr.is_bind_c
|| lvalue->ts.u.derived->attr.sequence))))
- gfc_error ("Data-pointer-object &L must be unlimited "
+ gfc_error ("Data-pointer-object at %L must be unlimited "
"polymorphic, a sequence derived type or of a "
- "type with the BIND attribute assignment at %L "
+ "type with the BIND attribute assignment "
"to be compatible with an unlimited polymorphic "
"target", &lvalue->where);
else
?
next prev parent reply other threads:[~2015-04-13 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 9:12 [Bug fortran/65751] New: " burnus at gcc dot gnu.org
2015-04-13 13:46 ` dominiq at lps dot ens.fr [this message]
2015-06-04 19:14 ` [Bug fortran/65751] " tkoenig at gcc dot gnu.org
2015-06-05 9:58 ` manu 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=bug-65751-4-RKprDImnGR@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).