From: Gerald Pfeifer <gerald@pfeifer.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [wwwdocs] gcc-13/changes.html + projects/gomp/: OpenMP update
Date: Sat, 14 Jan 2023 22:47:26 +0100 (CET) [thread overview]
Message-ID: <9a83714b-d74f-3db9-6b93-533f1631c642@pfeifer.com> (raw)
In-Reply-To: <008db493-fd5d-b5ca-69ae-369c630c13e6@codesourcery.com>
Hi Tobias,
On Fri, 2 Sep 2022, Tobias Burnus wrote:
> Update the OpenMP status for features that were added in the last months.
I made a couple of incremental edits. See below for what I just pushed
(and please speak up if you see any issues).
Gerald
commit 2f870cba5aaaa8c81449beb618a9030824360a25
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date: Sat Jan 14 22:44:49 2023 +0100
gcc-13: Various editorial changes around OMP entries
diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 96d47903..08e36fb3 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -54,10 +54,10 @@ a work-in-progress.</p>
<ul>
<li>
Reverse offload is now supported and the all clauses to the
- <code>requires</code> directive are now accepted; however, 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 cause that the
- only available device is the initial device (the host). Fortran now
+ 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.
</li>
<li>
@@ -72,27 +72,27 @@ a work-in-progress.</p>
syntax in C/C++ and device-specific ICV settings with environment variables
are now supported.</li>
<li>
- Initial support for OpenMP 5.2 features have been added: Support for
+ Initial support for OpenMP 5.2 features has been added:
<code>firstprivate</code> and <code>allocate</code> clauses on the
- <code>scope</code> construct and the OpenMP 5.2 syntax of the
- <code>linear</code> clause; the new enum/constants
+ <code>scope</code> construct; the OpenMP 5.2 syntax of the
+ <code>linear</code> clause; new enum/constants
<code>omp_initial_device</code> and <code>omp_invalid_device</code>; and
optionally omitting the map-type in <code>target enter/exit data</code>.
The <code>enter</code> clause (as alias for <code>to</code>) has been added
- to the <code>declare target</code> directive. Also added has been the
+ to the <code>declare target</code> directive. Also added have been the
<code>omp_in_explicit_task</code> routine and the <code>doacross</code>
clause as alias for <code>depend</code> with
<code>source</code>/<code>sink</code> modifier.
</li>
<li>
- The <code>_ALL</code> suffix to the device-scope environment variables,
+ The <code>_ALL</code> suffix to the device-scope environment variables
added in Technical Report (TR11) is already handled.
</li>
<li>
For user defined allocators requesting high bandwidth or large capacity
memspaces or interleaved partitioning, the <a
href="http://memkind.github.io/memkind/">memkind</a> library is used,
- if available at runtime.
+ if available at run time.
</li>
</ul>
</li>
next prev parent reply other threads:[~2023-01-14 21:47 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 [this message]
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=9a83714b-d74f-3db9-6b93-533f1631c642@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).