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. cbf7dcbf8cddc08c0cefb04a1d5f5d78c35224ed Date: Fri, 24 Nov 2023 16:46:00 +0000 (GMT) [thread overview] Message-ID: <20231124164600.D990B3858C66@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 cbf7dcbf8cddc08c0cefb04a1d5f5d78c35224ed (commit) from dc54aeee47a0a7cd24220c27788e2ce3ddd6e4c5 (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 cbf7dcbf8cddc08c0cefb04a1d5f5d78c35224ed Author: Tobias Burnus <tobias@codesourcery.com> Date: Fri Nov 24 17:45:45 2023 +0100 gcc-14/changes.html: Fix HTML syntax diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index 4eac9d6e..6c42b61f 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/changes.html @@ -53,9 +53,10 @@ a work-in-progress.</p> The <code>requires</code> directive's <code>unified_address</code> requirement is now fulfilled by both AMD GCN and nvptx devices. </li> - <li>OpenMP 5.0: The <code>allocate/<code> directive is now + <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. + </li> <li> OpenMP 5.1: Support was added for collapsing imperfectly nested loops and using <code>present</code> as map-type modifier and in ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-14/changes.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-11-24 16:46 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=20231124164600.D990B3858C66@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).