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-13/changes.html + projects/gomp/: OpenMP update
Date: Thu, 8 Sep 2022 17:40:09 +0200 [thread overview]
Message-ID: <YxoM2U6f3VPBLrgU@tucnak> (raw)
In-Reply-To: <008db493-fd5d-b5ca-69ae-369c630c13e6@codesourcery.com>
On Fri, Sep 02, 2022 at 09:37:57AM +0200, Tobias Burnus wrote:
> Update the OpenMP status for features that were added in the last months.
>
> Comments/suggestions? Okay to commit?
>
> 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
> gcc-13/changes.html + projects/gomp/: OpenMP update
>
> * htdocs/gcc-13/changes.html: Update OpenMP entry; fix html syntax.
> * htdocs/projects/gomp/index.html: Update OpenMP 5.x implementation status;
> add missing item from libgomp.texi + flip two items to have same order as
> the .texi.
>
> htdocs/gcc-13/changes.html | 42 ++++++++++++++++++++++++++++++++---------
> htdocs/projects/gomp/index.html | 40 +++++++++++++++++++++++++++++----------
> 2 files changed, 63 insertions(+), 19 deletions(-)
I think some of the </li> or <tr> issues have been fixed in the mean time,
so it might not apply cleanly.
LGTM, whether you want to update it further for doacross/omp_cur_iteration
now or whether we do it incrementally up to you.
Jakub
next prev parent reply other threads:[~2022-09-08 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 7:37 Tobias Burnus
2022-09-08 15:40 ` Jakub Jelinek [this message]
2023-01-14 21:47 ` Gerald Pfeifer
2023-01-16 8:17 ` Tobias Burnus
2023-01-16 22:16 ` Gerald Pfeifer
2023-01-18 12:39 ` Tobias Burnus
2023-01-20 17:50 ` Jakub Jelinek
2023-01-21 12:48 ` Gerald Pfeifer
2023-01-21 12:53 ` Tobias Burnus
2023-01-23 9:00 ` Tobias Burnus
2023-01-23 9:06 ` 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=YxoM2U6f3VPBLrgU@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).