From: Gerald Pfeifer <gerald@pfeifer.com>
To: Paul Hua <paul.hua.gm@gmail.com>
Cc: Matthew Fortune <mfortune@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [wwwdoc][Patch] Mention Loongson 3a1000 3a2000 3a3000 2k1000 support in gcc9
Date: Mon, 16 Jan 2023 21:07:53 +0100 (CET) [thread overview]
Message-ID: <d226dc47-4290-988c-d47f-977d61bb30c5@pfeifer.com> (raw)
In-Reply-To: <CAKjxQHkKXEPTy1ZqeQxjrZgVE0AtZ_0reYQyfRyfYziUzo2otg@mail.gmail.com>
On Thu, 4 Apr 2019, Paul Hua wrote:
> This is a updated version, Ok for commit?
Yikes - yes! Apologies, I somehow missed that mail back then (in the
middle of two weeks essentially off the grid).
I pushed your patch with some minor changes; see below.
Gerald
commit bfea0a7904c170d262ca4b18ae02b97d15625424
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date: Mon Jan 16 21:04:47 2023 +0100
gcc-9: Mention Loongson 3a1000 3a2000 3a3000 2k1000 support
Originally by Paul Hua <paul.hua.gm@gmail.com>.
diff --git a/htdocs/gcc-9/changes.html b/htdocs/gcc-9/changes.html
index ffaf4824..7dfae89c 100644
--- a/htdocs/gcc-9/changes.html
+++ b/htdocs/gcc-9/changes.html
@@ -945,8 +945,44 @@ $ g++ typo.cc
</li>
</ul>
-
-<!-- <h3 id="mips">MIPS</h3> -->
+<h3 id="mips">MIPS</h3>
+<ul>
+ <li>
+ The Loongson <code>loongson-mmi</code> and <code>loongson-ext</code>
+ extensions have been split from <code>loongson3a</code>:
+ <ul>
+ <li><code>loongson-mmi</code> contains
+ the Loongson MMI (MultiMedia extensions Instructions).</li>
+ <li><code>loongson-ext</code> contains
+ the Loongson EXT (EXTensions instructions).</li>
+ </ul>
+ </li>
+ <li>
+ The Loongson EXT2 (EXTensions R2 instructions) are now supported.
+ <ul>
+ <li><code>loongson-ext2</code> contains the Loongson EXT2 instructions.</li>
+ </ul>
+ Command-line options<code>-m[no-]loongson-mmi</code>,
+ <code>-m[no-]loongson-ext</code>, and <code>-m[no-]loongson-ext2</code>
+ enable or disable those extensions.
+ </li>
+ <li>
+ Support has been added for the following processors
+ (GCC identifiers in parentheses):
+ <ul>
+ <li>Loongson 3A1000 (<code>gs464</code>)
+ which enables <code>loongson-mmi</code>, <code>loongson-ext</code> by default.</li>
+ <li>Loongson 3A2000/3A3000 (<code>gs464e</code>)
+ which enables <code>loongson-mmi</code>, <code>loongson-ext</code>, <code>loongson-ext2</code> by default.</li>
+ <li>Loongson 2K1000 (<code>gs264e</code>)
+ which enables <code>loongson-ext</code>, <code>loongson-ext2</code>, <code>msa</code> by default.</li>
+ </ul>
+ The GCC identifiers can be used as arguments to the <code>-mcpu</code>
+ and <code>-mtune</code> options (as in <code>-mcpu=gs464</code> or
+ <code>-mtune=gs464e</code>) or as arguments to the equivalent target
+ attributes and pragmas.
+ </li>
+</ul>
<!-- <h3 id="mep">MeP</h3> -->
prev parent reply other threads:[~2023-01-16 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 12:32 Paul Hua
2019-01-12 10:50 ` Paul Hua
2019-01-13 23:46 ` Gerald Pfeifer
2019-01-17 2:05 ` Paul Hua
2019-04-04 5:02 ` Paul Hua
2023-01-16 20:07 ` Gerald Pfeifer [this message]
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=d226dc47-4290-988c-d47f-977d61bb30c5@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mfortune@gmail.com \
--cc=paul.hua.gm@gmail.com \
/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: 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).