public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Andre Simoes Dias Vieira <avieira@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. fbebf7a1d7aa87bd33780d549990bb22cf3aaeca Date: Fri, 24 Apr 2020 09:12:29 +0000 (GMT) [thread overview] Message-ID: <20200424091229.0DC2938930D5@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 fbebf7a1d7aa87bd33780d549990bb22cf3aaeca (commit) from 967663179682d6f626c250132e1cfc9013ea414d (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 fbebf7a1d7aa87bd33780d549990bb22cf3aaeca Author: Andre Vieira <andre.simoesdiasvieira@arm.com> Date: Wed Apr 22 17:23:19 2020 +0100 wwwdocs: Add -moutline-atomics for AArch64 on gcc-9.4 and gcc-8.5 diff --git a/htdocs/gcc-8/changes.html b/htdocs/gcc-8/changes.html index 83dd1bc0..83e57db1 100644 --- a/htdocs/gcc-8/changes.html +++ b/htdocs/gcc-8/changes.html @@ -1394,5 +1394,22 @@ known to be fixed in the 8.4 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="GCC8.5">GCC 8.5</h2> + +<h3> Target Specific Changes</h3> + +<h4>AArch64</h4> + <ul> + <li> + The option <code>-moutline-atomics</code> has been added to aid + deployment of the Large System Extensions (LSE) on GNU/Linux systems built + with a baseline architecture targeting Armv8-A. When the option is + specified code is emitted to detect the presence of LSE instructions at + runtime and use them for standard atomic operations. + For more information please refer to the documentation. + </li> + </ul> + </body> </html> diff --git a/htdocs/gcc-9/changes.html b/htdocs/gcc-9/changes.html index 74c7cde7..a2a28a9a 100644 --- a/htdocs/gcc-9/changes.html +++ b/htdocs/gcc-9/changes.html @@ -1132,5 +1132,21 @@ complete (that is, it is possible that some PRs that have been fixed are not listed here).</p> <!-- .................................................................. --> +<h2 id="GCC9.4">GCC 9.4</h2> + +<h3> Target Specific Changes</h3> + +<h4>AArch64</h4> + <ul> + <li> + The option <code>-moutline-atomics</code> has been added to aid + deployment of the Large System Extensions (LSE) on GNU/Linux systems built + with a baseline architecture targeting Armv8-A. When the option is + specified code is emitted to detect the presence of LSE instructions at + runtime and use them for standard atomic operations. + For more information please refer to the documentation. + </li> + </ul> + </body> </html> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-8/changes.html | 17 +++++++++++++++++ htdocs/gcc-9/changes.html | 16 ++++++++++++++++ 2 files changed, 33 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-04-24 9:12 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=20200424091229.0DC2938930D5@sourceware.org \ --to=avieira@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).