From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: [wwwdocs] gcc-12/changes.html: OpenMP 5.1 update (was: [wwwdocs] gcc-12/changes.html: OpenMP - mention masked support)
Date: Mon, 6 Sep 2021 15:44:03 +0200 [thread overview]
Message-ID: <20210906134403.GY920497@tucnak> (raw)
In-Reply-To: <8c3348aa-9bac-5bfc-f4f1-a1e418cca351@codesourcery.com>
On Mon, Sep 06, 2021 at 03:20:44PM +0200, Tobias Burnus wrote:
> On 13.08.21 16:37, Tobias Burnus wrote:
>
> > Update the OpenMP section again, now that Jakub has added the 'masked'
> > construct.
> > Comments?
>
> Jakub did comment on IRC that it probably makes sense to do less
> frequent commits.
> Thus, I waited a while and now have an update list. Besides 'masked' it
> now mentions:
>
> scope construct; nothing and error directive + primary in proc_bind.
>
> OK? Comments? Suggestions?
>
> Tobias
>
> PS: Also new that the existing 'device' clause now supports the
> modifiers 'device_num' and 'ancestor' and a bunch of bug fixes. While
> very useful, I think those aren't changes.html worthy.
Agreed (especially because the ancestor modifier is only parsing, but
eventually runs into sorry_at for missing reverse_offload support).
Ok, thanks.
Jakub
next prev parent reply other threads:[~2021-09-06 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 14:37 [wwwdocs] gcc-12/changes.html: OpenMP - mention masked support Tobias Burnus
2021-09-06 13:20 ` [wwwdocs] gcc-12/changes.html: OpenMP 5.1 update (was: [wwwdocs] gcc-12/changes.html: OpenMP - mention masked support) Tobias Burnus
2021-09-06 13:44 ` Jakub Jelinek [this message]
2023-01-16 23:42 ` [wwwdocs] gcc-12/changes.html: OpenMP - mention masked support Gerald Pfeifer
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=20210906134403.GY920497@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--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).