public inbox for
help / color / mirror / Atom feed
From: Kyrylo Tkachov <>
Subject: gcc-wwwdocs branch master updated. b034528ab0b49be051a1cc27467b0e65c812c8db
Date: Tue, 23 Mar 2021 14:13:52 +0000 (GMT)	[thread overview]
Message-ID: <> (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  b034528ab0b49be051a1cc27467b0e65c812c8db (commit)
      from  0913e2692a157b96957112d04f12497fd174ccae (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 b034528ab0b49be051a1cc27467b0e65c812c8db
Author: Kyrylo Tkachov <>
Date:   Tue Mar 23 14:12:51 2021 +0000

    aarch64: Add note about Random Number intrinsics fix

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 22bf54bb..5fc81be6 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -1124,6 +1124,10 @@ are not listed here).</p>
+  <li>
+  A bug with the Random Number intrinsics in the <code>arm_acle.h</code> header
+  that resulted in an incorrect status result being returned has been fixed.
+  </li>
   <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,


Summary of changes:
 htdocs/gcc-10/changes.html | 4 ++++
 1 file changed, 4 insertions(+)


                 reply	other threads:[~2021-03-23 14: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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be 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).