public inbox for
help / color / mirror / Atom feed
From: Gerald Pfeifer <>
Subject: gcc-wwwdocs branch master updated. 2f870cba5aaaa8c81449beb618a9030824360a25
Date: Sat, 14 Jan 2023 21:45:57 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  2f870cba5aaaa8c81449beb618a9030824360a25 (commit)
      from  acd58a986d9d28bc0d9b78caf7317840ee286b73 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 2f870cba5aaaa8c81449beb618a9030824360a25
Author: Gerald Pfeifer <>
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>
       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.
@@ -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>
-      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.
-      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.
       For user defined allocators requesting high bandwidth or large capacity
       memspaces or interleaved partitioning, the <a
       href="">memkind</a> library is used,
-      if available at runtime.
+      if available at run time.


Summary of changes:
 htdocs/gcc-13/changes.html | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)


                 reply	other threads:[~2023-01-14 21:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).