public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Chenghua Xu <paulhua@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 8d3f0483708a39f9ebdea6bc2f713fba71c57d16 Date: Sun, 8 May 2022 01:48:44 +0000 (GMT) [thread overview] Message-ID: <20220508014844.933F63858C53@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 8d3f0483708a39f9ebdea6bc2f713fba71c57d16 (commit) from 7dc6962f7d3ab17d02619ca25b261bf37d5ef31c (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 8d3f0483708a39f9ebdea6bc2f713fba71c57d16 Author: Chenghua Xu <xuchenghua@loongson.cn> Date: Sun May 8 09:46:46 2022 +0800 Fix typo in Added LoongArch support commit. diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index f77ea5ad..3fb33ad9 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -699,7 +699,7 @@ function Multiply (S1, S2 : Sign) return Sign is <ul> <li>Support for the LoongArch architecture instruction set has been added.</li> <li>The Loongson CPU codename LA464 and LoongArch generic CPU codename loongarch64 - are supported through the <code>-march=</code> and <code>-march=</code> options + are supported through the <code>-march=</code> and <code>-mtune=</code> options (GCC identifiers in parentheses).</li> <ul> <li>Loongson LA464 core (<code>la464</code>).</li> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-05-08 1:48 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=20220508014844.933F63858C53@sourceware.org \ --to=paulhua@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).