public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 01a1afc13afd0e2b981262b0a1bf9ba1d7d19f79 Date: Fri, 13 May 2022 22:29:00 +0000 (GMT) [thread overview] Message-ID: <20220513222900.561FF395A450@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 01a1afc13afd0e2b981262b0a1bf9ba1d7d19f79 (commit) from 43a15bdeeda8b1bac296a2ca0f0e6a901b0de488 (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 01a1afc13afd0e2b981262b0a1bf9ba1d7d19f79 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Sat May 14 00:27:52 2022 +0200 gcc-12: Fix markup in the Loongson section diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index eb144a86..a32f1d53 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -700,11 +700,12 @@ function Multiply (S1, S2 : Sign) return Sign is <li>Support for the LoongArch architecture instruction set has been added.</li> <li>The Loongson CPU codename LA464 and LoongArch 64-bit generic CPU codename loongarch64 are supported through the <code>-march=</code> and <code>-mtune=</code> options - (GCC identifiers in parentheses).</li> + (GCC identifiers in parentheses). <ul> <li>Loongson LA464 core (<code>la464</code>).</li> <li>LoongArch 64-bit generic core (<code>loongarch64</code>).</li> </ul> + </li> </ul> <h3 id="mips">MIPS</h3> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-05-13 22:29 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=20220513222900.561FF395A450@sourceware.org \ --to=gerald@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).