public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Kyrylo Tkachov <ktkachov@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 8c7f1cea627ad41962329f626ad3e8c90c7e49d4 Date: Thu, 23 Apr 2020 08:13:08 +0000 (GMT) [thread overview] Message-ID: <20200423081308.754A53851C2D@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 8c7f1cea627ad41962329f626ad3e8c90c7e49d4 (commit) from cb7aff9c268dcb7012ea1d72dee82f64b0c9de12 (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 8c7f1cea627ad41962329f626ad3e8c90c7e49d4 Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com> Date: Thu Apr 23 09:12:50 2020 +0100 [AArch64] Fix typo in sve2-aes in GCC 10 changes.html diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index 3146806b..fc360220 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -642,7 +642,7 @@ typedef svbool_t pred512 __attribute__((arm_sve_vector_bits(512))); through autovectorization. It can be enabled through the <code>+sve2</code> option extension (for example, <code>-march=armv8.5-a+sve2</code>). Additional extensions can be enabled through <code>+sve2-sm4</code>, - <code>+sve2=aes</code>, <code>+sve2-sha3</code> and + <code>+sve2-aes</code>, <code>+sve2-sha3</code> and <code>+sve2-bitperm</code>. </li> <li> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-10/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-04-23 8:13 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=20200423081308.754A53851C2D@sourceware.org \ --to=ktkachov@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).