public inbox for
help / color / mirror / Atom feed
From: Kyrylo Tkachov <>
Subject: gcc-wwwdocs branch master updated. c29a76bd12e67fe3bfae112cc1f7ed16b22b592a
Date: Tue, 23 Mar 2021 14:18:46 +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  c29a76bd12e67fe3bfae112cc1f7ed16b22b592a (commit)
      from  b034528ab0b49be051a1cc27467b0e65c812c8db (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 c29a76bd12e67fe3bfae112cc1f7ed16b22b592a
Author: Kyrylo Tkachov <>
Date:   Tue Mar 23 14:15:18 2021 +0000

    aarch64: Use GCC 11 rather than GCC 11.0

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 69869309..667e0cb9 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -566,7 +566,7 @@ a work-in-progress.</p>
   is supported with the <code>-mharden-sls=</code> option.  Please refer to the
   documentation for usage instructions.</li>
   <li>The availability of Advanced SIMD intrinsics available through the
-  <code>arm_neon.h</code> header is improved and GCC 11.0 supports the full
+  <code>arm_neon.h</code> header is improved and GCC 11 supports the full
   set of intrinsics defined by ACLE Q3 2020.</li>


Summary of changes:
 htdocs/gcc-11/changes.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


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