public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. df2bc49fc018c2b1aeb27030fe1967470d0d4ec3 Date: Fri, 1 Mar 2024 14:06:25 +0000 (GMT) [thread overview] Message-ID: <20240301140625.2486A3858D39@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 df2bc49fc018c2b1aeb27030fe1967470d0d4ec3 (commit) from 509d9104a9ae8246122c3d97b3e33ddf30416f93 (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 df2bc49fc018c2b1aeb27030fe1967470d0d4ec3 Author: Thomas Schwinge <tschwinge@baylibre.com> Date: Fri Mar 1 15:01:54 2024 +0100 Update GCC 14 OpenACC changes some more Follow-up to commit f92f353bb0e932edba7d063b2609943683cf0a36 "gcc-14/changes.html + projects/gomp/: OpenMP + OpenACC update": - 's%acc_alloc%acc_malloc' - add 'acc_map_data' and 'acc_unmap_data' - swap 'acc_deviceptr' and 'acc_hostptr' - 's%memcyp%memcpy%g' diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index e8004d4a..d88fbc96 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/changes.html @@ -120,12 +120,14 @@ a work-in-progress.</p> 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>openacc_lib.h</code> header file: + <code>acc_malloc</code>, <code>acc_free</code>, + <code>acc_map_data</code>, <code>acc_unmap_data</code>, + <code>acc_deviceptr</code>, <code>acc_hostptr</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>. + <code>acc_memcpy_from_device</code>, and + <code>acc_memcpy_from_device_async</code>. </ul> </li> <li>For offload-device code generated via OpenMP and OpenACC, the math ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-14/changes.html | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2024-03-01 14:06 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=20240301140625.2486A3858D39@sourceware.org \ --to=tschwinge@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).