public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/omp/gcc-12] libgomp.texi: Add more to-be-implemented OpenMP 5.2 features Date: Tue, 5 Jul 2022 08:10:53 +0000 (GMT) [thread overview] Message-ID: <20220705081053.A8D3B38582AD@sourceware.org> (raw) https://gcc.gnu.org/g:f29aac5bfd0c7a89bd3703b3b2b5f9a8e164e2cc commit f29aac5bfd0c7a89bd3703b3b2b5f9a8e164e2cc Author: Tobias Burnus <tobias@codesourcery.com> Date: Tue Jul 5 09:23:13 2022 +0200 libgomp.texi: Add more to-be-implemented OpenMP 5.2 features libgomp/ * libgomp.texi (Other new OpenMP 5.1 features): Add 'begin declare target'. (Other new OpenMP 5.2 features): New. (cherry picked from commit 8255b49ed8ab37fd61d85bb48f97c618f05a8392) Diff: --- libgomp/ChangeLog.omp | 9 +++++++++ libgomp/libgomp.texi | 17 ++++++++++++++++- 2 files changed, 25 insertions(+), 1 deletion(-) diff --git a/libgomp/ChangeLog.omp b/libgomp/ChangeLog.omp index d20fe4bdf7a..6225f015a48 100644 --- a/libgomp/ChangeLog.omp +++ b/libgomp/ChangeLog.omp @@ -1,3 +1,12 @@ +2022-07-05 Tobias Burnus <tobias@codesourcery.com> + + Backport from mainline: + 2022-05-27 Tobias Burnus <tobias@codesourcery.com> + + * libgomp.texi (Other new OpenMP 5.1 features): Add + 'begin declare target'. + (Other new OpenMP 5.2 features): New. + 2022-07-05 Tobias Burnus <tobias@codesourcery.com> Backport from mainline: diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi index 1f2f848ba73..2dfca4e9bb0 100644 --- a/libgomp/libgomp.texi +++ b/libgomp/libgomp.texi @@ -343,6 +343,7 @@ The OpenMP 4.5 specification is fully supported. @item Support of structured block sequences in C/C++ @tab Y @tab @item @code{unconstrained} and @code{reproducible} modifiers on @code{order} clause @tab Y @tab +@item Support @code{begin/end declare target} syntax in C/C++ @tab N @tab @end multitable @@ -387,7 +388,8 @@ The OpenMP 4.5 specification is fully supported. @item @code{allocate} and @code{firstprivate} clauses on @code{scope} @tab N @tab @item @code{ompt_callback_work} @tab N @tab -@item Extended map-type handling of @code{target enter/exit data} @tab N @tab +@item Default map-type for @code{map} clause in @code{target enter/exit data} + @tab N @tab @item New @code{doacross} clause as alias for @code{depend} with @code{source}/@code{sink} modifier @tab N @tab @item Deprecation of @code{depend} with @code{source}/@code{sink} modifier @@ -395,6 +397,19 @@ The OpenMP 4.5 specification is fully supported. @item @code{omp_cur_iteration} keyword @tab N @tab @end multitable +@unnumberedsubsec Other new OpenMP 5.2 features + +@multitable @columnfractions .60 .10 .25 +@headitem Description @tab Status @tab Comments +@item For Fortran, optional comma between directive and clause @tab N @tab +@item Conforming device numbers and @code{omp_initial_device} and + @code{omp_invalid_device} enum/PARAMETER @tab N @tab +@item Initial value of @emph{default-device-var} ICV with + @code{OMP_TARGET_OFFLOAD=mandatory} @tab N @tab +@item @emph{interop_types} in any position of the modifier list for the @code{init} clause + of the @code{interop} construct @tab N @tab +@end multitable + @c --------------------------------------------------------------------- @c OpenMP Runtime Library Routines
reply other threads:[~2022-07-05 8:10 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220705081053.A8D3B38582AD@sourceware.org \ --to=burnus@gcc.gnu.org \ --cc=gcc-cvs@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).