public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Richard Biener <rguenth@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 163634a2c8932f96bec2cadf51a7a7705ee73964 Date: Mon, 31 May 2021 07:37:00 +0000 (GMT) [thread overview] Message-ID: <20210531073700.7F08D3857807@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 163634a2c8932f96bec2cadf51a7a7705ee73964 (commit) from 68c7403bff82ca52fa9efcee7b041339715e1274 (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 163634a2c8932f96bec2cadf51a7a7705ee73964 Author: Richard Biener <rguenther@suse.de> Date: Mon May 31 09:36:05 2021 +0200 Document __builtin_shufflevector This documents the added __builtin_shufflevector extension for GCC 12. diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index 9fecc24b..42ded16d 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -64,7 +64,13 @@ a work-in-progress.</p> <!-- <h3 id="brig">BRIG (HSAIL)</h3> --> -<!-- <h3 id="c-family">C family</h3> --> +<h3 id="c-family">C family</h3> + +<ul> + <li>Support for <code>__builtin_shufflevector</code> compatible with + the clang language extension was added. + </li> +</ul> <!-- <h3 id="cxx">C++</h3> --> <!-- <h4 id="libstdcxx">Runtime Library (libstdc++)</h4> --> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-05-31 7:37 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=20210531073700.7F08D3857807@sourceware.org \ --to=rguenth@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).