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: Gerald Pfeifer <gerald@pfeifer.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [wwwdocs] gcc-13/changes.html + projects/gomp/: OpenMP update
Date: Fri, 20 Jan 2023 18:50:41 +0100	[thread overview]
Message-ID: <Y8rUcXFpgiwAQJHd@tucnak> (raw)
In-Reply-To: <82d62ca9-06d4-72d7-965b-eab5388fec90@codesourcery.com>

On Wed, Jan 18, 2023 at 01:39:43PM +0100, Tobias Burnus wrote:
> --- a/htdocs/gcc-13/changes.html
> +++ b/htdocs/gcc-13/changes.html
> @@ -53,12 +53,19 @@ a work-in-progress.</p>
>    <li id="openmp"><a href="https://gcc.gnu.org/projects/gomp/">OpenMP</a>
>    <ul>
>      <li>
> -      Reverse offload is now supported and the all clauses to the
> -      <code>requires</code> directive are now accepted. However, the
> -      <code>requires_offload</code>, <code>unified_address</code>
> -      and <code>unified_shared_memory</code> clauses imply the initial
> -      device (= the host) as the only available device. Fortran now
> -      supports non-rectangular loop nests, which were added for C/C++ in GCC 11.
> +      Reverse offload is now supported with nvptx devices. Additionally, the
> +      <code>requires</code> handling has been improved and all clauses are
> +      now accepted. If a requirement cannot be fulfilled for an accessible
> +      device, this device is excluded from the list of available devices. This
> +      may imply that the only device left is the host (the initial device).
> +      In particular, <code>requires_offload</code> is currently unsupported on
> +      AMD GCN devices while <code>unified_address</code> and
> +      <code>unified_shared_memory</code> are unsupported by all non-host
> +      devices.

The above looks good to me.

> +    </li>
> +    <li>
> +      OpenMP 5.0: Fortran now supports non-rectangular loop nests, which were
> +      added for C/C++ in GCC 11.

But because of the sorry_at I'd say "supports some" instead of "supports".
And similarly in the libgomp texi as well as gomp/index.html clarify it is
full C/C++ support (I'll look at PR108435 soon) and say the Fortran support
is still partial.

> --- a/htdocs/projects/gomp/index.html
> +++ b/htdocs/projects/gomp/index.html
> @@ -547,9 +547,14 @@ than listed, depending on resolved corner cases and optimizations.</p>
>      <td></td>
>    </tr>
>    <tr>
> -    <td><code>align</code> clause/modifier in <code>allocate</code> directive/clause and <code>allocator</code> directive</td>
> +    <td><code>align</code> clause in <code>allocate</code> directive</td>
> +    <td class="unsupported">No</td>
> +    <td></td>
> +  </tr>
> +  <tr>
> +    <td><code>align</code> modifier in <code>allocate</code> clause</td>
>      <td class="supported"><a href="../../gcc-12/changes.html#languages">GCC&nbsp;12</a></td>
> -    <td>C/C++ on clause only</td>
> +    <td></td>
>    </tr>
>    <tr>
>      <td><code>thread_limit</code> clause to <code>target</code> construct</td>


	Jakub


  reply	other threads:[~2023-01-20 17:50 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
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 [this message]
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=Y8rUcXFpgiwAQJHd@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).