public inbox for
help / color / mirror / Atom feed
From: Gerald Pfeifer <>
Subject: gcc-wwwdocs branch master updated. 87fb03bc6ce3e190ba74215a9aad5021e263185a
Date: Sat, 21 May 2022 22:23:45 +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  87fb03bc6ce3e190ba74215a9aad5021e263185a (commit)
      from  02f3d8829d41a7f992f7f4a994913cb50e8418df (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 87fb03bc6ce3e190ba74215a9aad5021e263185a
Author: Gerald Pfeifer <>
Date:   Sun May 22 00:23:09 2022 +0200

    gcc-12: Editorial changes for RISC-V

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 0eae78ff..3b94378e 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -817,8 +817,8 @@ function Multiply (S1, S2 : Sign) return Sign is
 	support architecture testing marco and <code>-march=</code> parsing.</li>
     <li>The option <code>-mtune=thead-c906</code> is added to tune for T-HEAD
 	c906 cores.</li>
-    <li>libstdc++'s no longer attempts to detect built-in atomics,
-	distributions that have out-of-tree workarounds for
+    <li>libstdc++ no longer attempts to detect built-in atomics.
+	Distributions that have out-of-tree workarounds for
 	<code>-latomic</code> should check their ABIs again.</li>


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


                 reply	other threads:[~2022-05-21 22:23 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).