From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, fortran <fortran@gcc.gnu.org>
Subject: Re: [Patch] OpenMP: Add Fortran support for inoutset depend-kind (was: openmp: Add support for inoutset depend-kind)
Date: Wed, 18 May 2022 11:22:47 +0200 [thread overview]
Message-ID: <YoS653bh6fctPW+n@tucnak> (raw)
In-Reply-To: <f0f8ff1a-bc88-bfce-ad25-6c1696c5532c@codesourcery.com>
On Wed, May 18, 2022 at 11:02:27AM +0200, Tobias Burnus wrote:
> OpenMP: Add Fortran support for inoutset depend-kind
>
> Fortran additions to the C/C++ + ME/libgomp commit
> r13-556-g2c16eb3157f86ae561468c540caf8eb326106b5f
>
> gcc/fortran/ChangeLog:
>
> * gfortran.h (enum gfc_omp_depend_op): Add OMP_DEPEND_INOUTSET.
> (gfc_omp_clauses): Enlarge ENUM_BITFIELD.
> * dump-parse-tree.cc (show_omp_namelist, show_omp_clauses): Handle
> 'inoutset' depend modifier.
> * openmp.cc (gfc_match_omp_clauses, gfc_match_omp_depobj): Likewise.
> * trans-openmp.cc (gfc_trans_omp_clauses, gfc_trans_omp_depobj):
> Likewise.
>
> libgomp/ChangeLog:
>
> * libgomp.texi (OpenMP 5.1): Set 'inoutset' to Y.
> (OpenMP Context Selectors): Add missing comma.
> * testsuite/libgomp.fortran/depend-5.f90: Add inoutset test.
> * testsuite/libgomp.fortran/depend-6.f90: Likewise.
> * testsuite/libgomp.fortran/depend-7.f90: Likewise.
> * testsuite/libgomp.fortran/depend-inoutset-1.f90: New test.
>
> gcc/testsuite/ChangeLog:
>
> * gfortran.dg/gomp/all-memory-1.f90: Add inoutset test.
> * gfortran.dg/gomp/all-memory-2.f90: Likewise.
> * gfortran.dg/gomp/depobj-1.f90: Likewise.
> * gfortran.dg/gomp/depobj-2.f90: Likewise.
Ok, thanks.
Jakub
prev parent reply other threads:[~2022-05-18 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YoOpbE7VulnzWtfh@tucnak>
2022-05-18 9:02 ` Tobias Burnus
2022-05-18 9:22 ` Jakub Jelinek [this message]
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=YoS653bh6fctPW+n@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).