public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] libgomp.texi (OpenMP TR11 impl. status): Fix 'strict' item
Date: Thu, 2 Feb 2023 13:46:49 +0100	[thread overview]
Message-ID: <Y9uwuVu32M5jVf2H@tucnak> (raw)
In-Reply-To: <768cda84-807f-581d-ea0f-5a5d0027e686@codesourcery.com>

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


      reply	other threads:[~2023-02-02 12:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 11:19 Tobias Burnus
2023-02-02 12:46 ` 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=Y9uwuVu32M5jVf2H@tucnak \
    --to=jakub@redhat.com \
    --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).