From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: Re: [Patch] Fortran/OpenMP: Improve associate-name diagnostic [PR103039]
Date: Fri, 18 Mar 2022 14:21:09 +0100 [thread overview]
Message-ID: <YjSHRaJRN+ggwDjN@tucnak> (raw)
In-Reply-To: <51e942e2-b8f9-5f35-9a92-bc29e9d06bd5@codesourcery.com>
On Fri, Mar 18, 2022 at 02:15:11PM +0100, Tobias Burnus wrote:
> This patch addresses a side issue found when looking at PR103039.
>
> Namely instead of printing:
>
> 55 | !$omp parallel firstprivate(tt)
> | 1
> Error: ASSOCIATE name ‘__tmp_INTEGER_4’ in FIRSTPRIVATE clause at (1)
>
> With the patch, the error is:
>
> Error: Associate name ‘tt’ in FIRSTPRIVATE clause at (1)
>
> That is: It prints the proper name and it uses 'associate name'
> matching the Fortran standard – and takes into account that an
> associate name not only used with ASSOCIATE but also with
> SELECT TYPE, SELECT RANK, and (untested) CHANGE TEAMS.
>
> OK for mainline?
LGTM, thanks.
> Fortran/OpenMP: Improve associate-name diagnostic [PR103039]
>
> gcc/fortran/ChangeLog:
>
> PR fortran/103039
> * openmp.cc (resolve_omp_clauses): Improve associate-name diagnostic
> for select type/rank.
>
> gcc/testsuite/ChangeLog:
>
> PR fortran/103039
> * gfortran.dg/gomp/associate1.f90: Update dg-error.
> * gfortran.dg/gomp/associate2.f90: New test.
>
> gcc/fortran/openmp.cc | 12 +++--
> gcc/testsuite/gfortran.dg/gomp/associate1.f90 | 40 +++++++-------
> gcc/testsuite/gfortran.dg/gomp/associate2.f90 | 76 +++++++++++++++++++++++++++
> 3 files changed, 104 insertions(+), 24 deletions(-)
Jakub
next prev parent reply other threads:[~2022-03-18 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 13:15 Tobias Burnus
2022-03-18 13:21 ` Jakub Jelinek [this message]
2022-03-18 16:27 Tobias Burnus
2022-03-18 16:38 ` Jakub Jelinek
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=YjSHRaJRN+ggwDjN@tucnak \
--to=jakub@redhat.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tobias@codesourcery.com \
/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).