This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/65751] Bogus &L in error message
- From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 04 Jun 2015 19:14:00 +0000
- Subject: [Bug fortran/65751] Bogus &L in error message
- Auto-submitted: auto-generated
- References: <bug-65751-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65751
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #1)
> 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
>
> ?
Yes, I think so too.
Dominique, this patch is obvious; if you care to commit this, please go ahead.
And I think an English error message that points out the place of the error is
more useful than a native-language one which doesn't, so I would favor
backporting.