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-5649] libgomp.texi (OpenMP TR11 impl. status): Fix 'strict' item Date: Thu, 2 Feb 2023 11:11:18 +0000 (GMT) [thread overview] Message-ID: <20230202111118.7556D3858C60@sourceware.org> (raw) https://gcc.gnu.org/g:8da7476c5fa8870c2fcded48d3de95978434c1be commit r13-5649-g8da7476c5fa8870c2fcded48d3de95978434c1be Author: Tobias Burnus <tobias@codesourcery.com> Date: Thu Feb 2 12:05:58 2023 +0100 libgomp.texi (OpenMP TR11 impl. status): Fix 'strict' item Fix the 'strict' modifier status: it is already listed (as 'Y') for OpenMP 5.1 for num_task and grainsize; only strict on num_threads is new with TR11. libgomp/ * libgomp.texi (OpenMP TR11): Fix item for 'strict' modifier. Diff: --- libgomp/libgomp.texi | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi index 0aa653d3ace..1f84b050eb2 100644 --- a/libgomp/libgomp.texi +++ b/libgomp/libgomp.texi @@ -469,8 +469,7 @@ Technical Report (TR) 11 is the first preview for OpenMP 6.0. @item @code{omp_curr_progress_width} identifier @tab N @tab @item @code{safesync} clause to the @code{parallel} construct @tab N @tab @item @code{omp_get_max_progress_width} runtime routine @tab N @tab -@item @code{strict} modifier keyword to @code{num_threads}, @code{num_tasks} - and @code{grainsize} @tab N @tab +@item @code{strict} modifier keyword to @code{num_threads} @tab N @tab @item @code{memscope} clause to @code{atomic} and @code{flush} @tab N @tab @item Routines for obtaining memory spaces/allocators for shared/device memory @tab N @tab
reply other threads:[~2023-02-02 11:11 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=20230202111118.7556D3858C60@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).