public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/56985] gcc/fortran/resolve.c:920: "'%s' in cannot appear in COMMON ..." Date: Mon, 30 Aug 2021 11:53:17 +0000 [thread overview] Message-ID: <bug-56985-4-g7dw0npUPj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56985-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56985 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anlauf at gcc dot gnu.org --- Comment #2 from anlauf at gcc dot gnu.org --- Actually the following seems better to me, as the location is that of the declaration and not of the COMMON block: diff --git a/gcc/fortran/resolve.c b/gcc/fortran/resolve.c index f641d0d4dae..8e5ed1c032c 100644 --- a/gcc/fortran/resolve.c +++ b/gcc/fortran/resolve.c @@ -979,7 +979,7 @@ resolve_common_vars (gfc_common_head *common_block, bool named_common) } if (UNLIMITED_POLY (csym)) - gfc_error_now ("%qs in cannot appear in COMMON at %L " + gfc_error_now ("%qs at %L cannot appear in COMMON " "[F2008:C5100]", csym->name, &csym->declared_at); if (csym->ts.type != BT_DERIVED) The message is checked in gcc/testsuite/gfortran.dg/unlimited_polymorphic_2.f03
next prev parent reply other threads:[~2021-08-30 11:53 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-17 10:04 [Bug translation/56985] New: " stigge at antcom dot de 2021-08-30 2:53 ` [Bug fortran/56985] " pinskia at gcc dot gnu.org 2021-08-30 11:53 ` anlauf at gcc dot gnu.org [this message] 2021-08-31 18:32 ` anlauf at gcc dot gnu.org 2021-09-01 17:06 ` cvs-commit at gcc dot gnu.org 2021-09-01 17:08 ` anlauf 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-56985-4-g7dw0npUPj@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).