public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [committed] libgomp.texi (OpenMP TR11 impl. status): Fix 'strict' item
@ 2023-02-02 11:19 Tobias Burnus
  2023-02-02 12:46 ` Jakub Jelinek
  0 siblings, 1 reply; 2+ messages in thread
From: Tobias Burnus @ 2023-02-02 11:19 UTC (permalink / raw)
  To: gcc-patches; +Cc: Jakub Jelinek

[-- Attachment #1: Type: text/plain, Size: 487 bytes --]

There is less new in TR11 as claimed ... 'strict' on grainsize/num_tasks is already
in OpenMP 5.1, it is implemented and also listed as 'Y' under 5.1.
Only 'num_threads(strict: int-expr)' is new in TR11.

Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

[-- Attachment #2: committed.diff --]
[-- Type: text/x-patch, Size: 1257 bytes --]

commit 8da7476c5fa8870c2fcded48d3de95978434c1be
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 --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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [committed] libgomp.texi (OpenMP TR11 impl. status): Fix 'strict' item
  2023-02-02 11:19 [committed] libgomp.texi (OpenMP TR11 impl. status): Fix 'strict' item Tobias Burnus
@ 2023-02-02 12:46 ` Jakub Jelinek
  0 siblings, 0 replies; 2+ messages in thread
From: Jakub Jelinek @ 2023-02-02 12:46 UTC (permalink / raw)
  To: Tobias Burnus; +Cc: gcc-patches

On Thu, Feb 02, 2023 at 12:19:56PM +0100, Tobias Burnus wrote:
> There is less new in TR11 as claimed ... 'strict' on grainsize/num_tasks is already
> in OpenMP 5.1, it is implemented and also listed as 'Y' under 5.1.
> Only 'num_threads(strict: int-expr)' is new in TR11.
> 
> Tobias
> -----------------
> Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

> commit 8da7476c5fa8870c2fcded48d3de95978434c1be
> 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.

Ok.

	Jakub


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-02-02 12:46 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-02 11:19 [committed] libgomp.texi (OpenMP TR11 impl. status): Fix 'strict' item Tobias Burnus
2023-02-02 12:46 ` Jakub Jelinek

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).