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 r13-4500] libgomp.texi: Fix a OpenMP 5.2 and a TR11 impl-status item
Date: Tue, 6 Dec 2022 08:52:19 +0000 (GMT) [thread overview]
Message-ID: <20221206085219.2E29B383235C@sourceware.org> (raw)
https://gcc.gnu.org/g:9f80367e539839fff1df2c85fc2640638199fc9e
commit r13-4500-g9f80367e539839fff1df2c85fc2640638199fc9e
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Tue Dec 6 09:49:30 2022 +0100
libgomp.texi: Fix a OpenMP 5.2 and a TR11 impl-status item
libgomp/
* libgomp.texi (OpenMP 5.2): Add missing 'the'.
(TR11): Add missing '@tab N @tab'.
Diff:
---
libgomp/libgomp.texi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi
index 4caac497506..efa7d956a33 100644
--- a/libgomp/libgomp.texi
+++ b/libgomp/libgomp.texi
@@ -406,7 +406,7 @@ to address of matching mapped list item per 5.1, Sect. 2.21.7.2 @tab N @tab
@item @code{allocate} and @code{firstprivate} clauses on @code{scope}
@tab Y @tab
@item @code{ompt_callback_work} @tab N @tab
-@item Default map-type for @code{map} clause in @code{target enter/exit data}
+@item Default map-type for the @code{map} clause in @code{target enter/exit data}
@tab Y @tab
@item New @code{doacross} clause as alias for @code{depend} with
@code{source}/@code{sink} modifier @tab Y @tab
@@ -463,6 +463,7 @@ Technical Report (TR) 11 is the first preview for OpenMP 6.0.
@item @code{access} allocator trait changes @tab N @tab
@item Extension of @code{interop} operation of @code{append_args}, allowing all
modifiers of the @code{init} clause
+ @tab N @tab
@item @code{interop} clause to @code{dispatch} @tab N @tab
@item @code{apply} code to loop-transforming constructs @tab N @tab
@item @code{omp_curr_progress_width} identifier @tab N @tab
reply other threads:[~2022-12-06 8:52 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=20221206085219.2E29B383235C@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: 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).