public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Tobias Burnus <burnus@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. f92f353bb0e932edba7d063b2609943683cf0a36 Date: Wed, 28 Feb 2024 09:03:19 +0000 (GMT) [thread overview] Message-ID: <20240228090319.3A3BB3858C98@sourceware.org> (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 f92f353bb0e932edba7d063b2609943683cf0a36 (commit) from 8701b8c92366d2039147b4830657a5bad2cb460f (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 f92f353bb0e932edba7d063b2609943683cf0a36 Author: Tobias Burnus <tburnus@baylibre.com> Date: Wed Feb 28 10:02:46 2024 +0100 gcc-14/changes.html + projects/gomp/: OpenMP + OpenACC update Update OpenMP for two meanwhile implemented features (lvalue-expr in map, indirect now also in Fortran). Update OpenACC for one new feature (Fortran interface to exisiting C/C++ routines). diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index 85ccc54d..1a455cd8 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/changes.html @@ -79,7 +79,8 @@ a work-in-progress.</p> </li> <li>OpenMP 5.0: The <code>allocate</code> directive is now supported for stack variables in C and Fortran, including the OpenMP 5.1 - <code>align</code> modifier. For Fortran, OpenMP allocators can now be + <code>align</code> modifier. In C and C++ the <code>map</code> clause now + accepts lvalue expressions. For Fortran, OpenMP allocators can now be used for allocatables and pointers using the <code>allocate</code> directive and its OpenMP 5.2 replacement, the <code>allocators</code> directive; files using this allocator and all files that might directly @@ -91,8 +92,8 @@ a work-in-progress.</p> <li> OpenMP 5.1: Support was added for collapsing imperfectly nested loops and using <code>present</code> as map-type modifier and in - <code>defaultmap</code>. The <code>indirect</code> clause is now supported - for C and C++. The performance of copying strided data from or to nvptx + <code>defaultmap</code>. The <code>indirect</code> clause is now + supported. The performance of copying strided data from or to nvptx and AMD GPU devices using the OpenMP 5.1 routine <code>omp_target_memcpy_rect</code> has been improved. </li> @@ -117,6 +118,14 @@ a work-in-progress.</p> <li>OpenACC 2.7: The <code>self</code> clause was added to be used on compute constructs and the <code>default</code> clause for data constructs.</li> + <li>OpenACC 3.2: The following API routines are now available in + Fortran using the <code>openacc</code> module or the + <code>openacc_lib.h</code> header file: <code>acc_alloc</code>, + <code>acc_free</code>, <code>acc_hostptr</code>, + <code>acc_deviceptr</code>, <code>acc_memcpy_to_device</code>, + <code>acc_memcpy_to_device_async</code>, + <code>acc_memcyp_from_device</code>, and + <code>acc_memcyp_from_device_async</code>. </ul> </li> <li>For offload-device code generated via OpenMP and OpenACC, the math diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html index bf20bb88..8fdfb95a 100644 --- a/htdocs/projects/gomp/index.html +++ b/htdocs/projects/gomp/index.html @@ -489,7 +489,7 @@ than listed, depending on resolved corner cases and optimizations.</p> </tr> <tr> <td>C/C++'s lvalue expressions in <code>to</code>, <code>from</code> and <code>map</code> clauses</td> - <td class="unsupported">No</td> + <td class="supported"><a href="../../gcc-14/changes.html#languages">GCC 14</a></td> <td></td> </tr> <tr> @@ -714,8 +714,8 @@ than listed, depending on resolved corner cases and optimizations.</p> </tr> <tr> <td>Indirect calls to the device version of a procedure or function in target regions</td> - <td class="partial"><a href="../../gcc-14/changes.html#languages">GCC 14</a></td> - <td>Only C and C++</td> + <td class="supported"><a href="../../gcc-14/changes.html#languages">GCC 14</a></td> + <td></td> </tr> <tr> <td><code>interop</code> directive</td> @@ -756,8 +756,8 @@ than listed, depending on resolved corner cases and optimizations.</p> </tr> <tr> <td><code>indirect</code> clause in <code>declare target</code></td> - <td class="partial"><a href="../../gcc-14/changes.html#languages">GCC 14</a></td> - <td>Only C and C++</td> + <td class="supported"><a href="../../gcc-14/changes.html#languages">GCC 14</a></td> + <td></td> </tr> <tr> <td><code>device_type(nohost)</code>/<code>device_type(host)</code> for variables</td> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-14/changes.html | 15 ++++++++++++--- htdocs/projects/gomp/index.html | 10 +++++----- 2 files changed, 17 insertions(+), 8 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2024-02-28 9:03 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: 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=20240228090319.3A3BB3858C98@sourceware.org \ --to=burnus@sourceware.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.org \ /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: linkBe 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).