public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 43a15bdeeda8b1bac296a2ca0f0e6a901b0de488 Date: Fri, 13 May 2022 17:10:36 +0000 (GMT) [thread overview] Message-ID: <20220513171036.80F07395A451@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 43a15bdeeda8b1bac296a2ca0f0e6a901b0de488 (commit) from ba9497f35da1a971002d0cb59913448247f9f306 (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 43a15bdeeda8b1bac296a2ca0f0e6a901b0de488 Author: Palmer Dabbelt <palmer@rivosinc.com> Date: Thu Apr 28 11:04:57 2022 -0700 gcc-12/changes.html: Document the RISC-V libstdc++ -latomic detection diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index d645b15f..eb144a86 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -816,6 +816,9 @@ 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 + <code>-latomic</code> should check their ABIs again.</li> </li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 3 +++ 1 file changed, 3 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-05-13 17:10 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=20220513171036.80F07395A451@sourceware.org \ --to=palmer@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).