public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. d2f0049d34088519fa28c7c6c1ee62d239523258 Date: Fri, 7 Aug 2020 09:49:35 +0000 (GMT) [thread overview] Message-ID: <20200807094935.172F93858D35@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 d2f0049d34088519fa28c7c6c1ee62d239523258 (commit) from 297d7c3deb3013f6546ce4faa7ba82fbca46201f (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 d2f0049d34088519fa28c7c6c1ee62d239523258 Author: Richard Sandiford <richard.sandiford@arm.com> Date: Fri Aug 7 10:49:23 2020 +0100 Document A64FX support in GCC 10.3 diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index b40f9a57..1a9e3ab7 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -1093,6 +1093,23 @@ known to be fixed in the 10.2 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here).</p> +<!-- .................................................................. --> +<h2 id="GCC10.3">GCC 10.3</h2> + +<h3>Target Specific Changes</h3> + +<h4>AArch64</h4> +<ul> + <li>GCC now supports the Fujitsu A64FX. The associated <code>-mcpu</code> + and <code>-mtune</code> options are <code>-mcpu=a64fx</code> and + <code>-mtune=a64fx</code> respectively. In particular, + <code>-mcpu=a64fx</code> generates code for Armv8.2-A with SVE and + tunes the code for the A64FX. This includes tuning the SVE code, + although by default the code is still length-agnostic and so works for + all SVE implementations. Adding <code>-msve-vector-bits=512</code> + makes the code specific to 512-bit SVE.</li> +</ul> + <!-- .................................................................. --> </body> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-10/changes.html | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-08-07 9:49 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=20200807094935.172F93858D35@sourceware.org \ --to=rsandifo@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).