From: Tobias Burnus <tobias@codesourcery.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Subject: *PING* - [wwwdocs] projects/gomp: TR11 + GCC13 update
Date: Wed, 23 Nov 2022 10:34:39 +0100 [thread overview]
Message-ID: <2e550e56-3b30-1cc9-0654-2e68896fae44@codesourcery.com> (raw)
In-Reply-To: <853627e4-b2a4-1c50-9d91-cdbb8396cca0@siemens.com>
On 11.11.22 16:13, Tobias Burnus wrote:
> This patch adds TR11 to the history of OpenMP releases – and it does
> an update of the implementation status.
>
> OK?
>
> Tobias
>
> PS: The implementation-status changes were lying around in that file
> for a while. I think both the GCC 13 release notes and this file needs
> some update for more recent changes. Nonetheless, while incomplete,
> the changes themselves should be fine.
-----------------
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
next prev parent reply other threads:[~2022-11-23 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 15:13 Tobias Burnus
2022-11-23 9:34 ` Tobias Burnus [this message]
2022-11-23 11:08 ` *PING* - " Jakub Jelinek
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=2e550e56-3b30-1cc9-0654-2e68896fae44@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).