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>,
	Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: [wwwdocs] gcc-13/changes.html + projects/gomp: OpenMP GCC 13 update
Date: Tue, 6 Dec 2022 10:15:01 +0100	[thread overview]
Message-ID: <Y48IFZkFP706KvCs@tucnak> (raw)
In-Reply-To: <4f17329b-0550-780d-e55b-49b2dbcd1ea9@codesourcery.com>

On Tue, Dec 06, 2022 at 09:59:17AM +0100, Tobias Burnus wrote:
> This patch updates the OpenMP implementation status, based on libgomp.texi.
> For the release notes, it also moves 'non-rectangular loop nests' up as that's
> a 5.0 not a 5.1 feature.
> And in line with libgomp.texi, it adds to projects/gomp/ the items for TR11,
> a OpenMP 6.0 preview. (Hence, the id="omp6.0" to have a fixed id even when
> the list is updated to TR12 and later OpenMP 6.0.)

The posted patch is certainly good, but doesn't do what you wrote above.

> PS: There will be surely more updates before GCC 13 is released; I hope/assume
> the next change will be for nvptx reverse offload...
> -----------------
> 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 9f80367e539839fff1df2c85fc2640638199fc9e
> Author: Tobias Burnus <tobias@codesourcery.com>
> Date:   Tue Dec 6 09:49:30 2022 +0100
> 
>     libgomp.texi: Fix a OpenMP 5.2 and a TR11 impl-status item
>     
>     libgomp/
>             * libgomp.texi (OpenMP 5.2): Add missing 'the'.
>             (TR11): Add missing '@tab N @tab'.
> ---
>  libgomp/libgomp.texi | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi
> index 4caac497506..efa7d956a33 100644
> --- a/libgomp/libgomp.texi
> +++ b/libgomp/libgomp.texi
> @@ -406,7 +406,7 @@ to address of matching mapped list item per 5.1, Sect. 2.21.7.2 @tab N @tab
>  @item @code{allocate} and @code{firstprivate} clauses on @code{scope}
>        @tab Y @tab
>  @item @code{ompt_callback_work} @tab N @tab
> -@item Default map-type for @code{map} clause in @code{target enter/exit data}
> +@item Default map-type for the @code{map} clause in @code{target enter/exit data}
>        @tab Y @tab
>  @item New @code{doacross} clause as alias for @code{depend} with
>        @code{source}/@code{sink} modifier @tab Y @tab
> @@ -463,6 +463,7 @@ Technical Report (TR) 11 is the first preview for OpenMP 6.0.
>  @item @code{access} allocator trait changes @tab N @tab
>  @item Extension of @code{interop} operation of @code{append_args}, allowing all
>        modifiers of the @code{init} clause
> +      @tab N @tab
>  @item @code{interop} clause to @code{dispatch} @tab N @tab
>  @item @code{apply} code to loop-transforming constructs @tab N @tab
>  @item @code{omp_curr_progress_width} identifier @tab N @tab


	Jakub


  reply	other threads:[~2022-12-06  9:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06  8:59 Tobias Burnus
2022-12-06  9:15 ` Jakub Jelinek [this message]
2022-12-06  9:32   ` Tobias Burnus
2022-12-06  9:42     ` 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=Y48IFZkFP706KvCs@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).