From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Harald Anlauf via Fortran <fortran@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fortran: diagnose USE associated symbols in COMMON blocks [PR108453]
Date: Sat, 28 Jan 2023 12:03:08 -0800 [thread overview]
Message-ID: <Y9V/fC4vZF++QHHM@troutmask.apl.washington.edu> (raw)
In-Reply-To: <trinity-26885791-f651-4f0a-a2c7-0c03ca90b149-1674925670220@3c-app-gmx-bs11>
On Sat, Jan 28, 2023 at 06:07:50PM +0100, Harald Anlauf via Fortran wrote:
>
> a USE associated symbol shall not appear in a COMMON block
> (F2018:C8121) and needs to be diagnosed. The patch is
> fairly obvious.
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>
> As the PR is marked as a 10/11/12/13 regression,
> I plan to backport as appropriate.
>
Yes. Backports are fine with a clean regression test.
Thanks for the patch and your continued attack on
bugzilla issues.
--
Steve
next prev parent reply other threads:[~2023-01-28 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 17:07 Harald Anlauf
2023-01-28 20:03 ` Steve Kargl [this message]
2023-01-28 20:04 ` Jerry D
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=Y9V/fC4vZF++QHHM@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).