From: Paul Hua <paul.hua.gm@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [wwwdoc][Patch] Mention Loongson 3a1000 3a2000 3a3000 2k1000 support in gcc9
Date: Mon, 31 Dec 2018 12:32:00 -0000 [thread overview]
Message-ID: <CAKjxQHkbwOD2pgu-gHdYgri-TSqmMGc-GNCB2aXSOh3dtfVVMA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 109 bytes --]
Hi Gerald,
The attached patch mention Loongson 3a1000 3a2000 3a3000 2k1000 support in gcc9.
ok for commit?
[-- Attachment #2: mention-loongson-3a1000-3a2000-3a3000-2k1000-support-in-gcc9.patch --]
[-- Type: text/x-patch, Size: 2110 bytes --]
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-9/changes.html,v
retrieving revision 1.30
diff -u -r1.30 changes.html
--- changes.html 3 Dec 2018 17:20:20 -0000 1.30
+++ changes.html 31 Dec 2018 10:21:32 -0000
@@ -214,6 +214,44 @@
</li>
</ul>
+<h3 id="mips">MIPS</h3>
+<ul>
+ <li>
+ The Loongson <code>loongson-mmi</code> and <code>loongson-ext</code>
+ extension has now been splited from <code>loongson3a</code>:
+ <ul>
+ <li><code>loongson-mmi</code> which contains
+ the Loongson MultiMedia extension Instructions operations.</li>
+ <li><code>loongson-ext</code> which contains
+ the Loongson EXTension instructions.</li>
+ </ul>
+ <li>
+ The Loongson EXTension R2 instructions is now supported.
+ <ul>
+ <li><code>loongson-ext2</code> which contains the Loongson EXTension R2 instructions.</li>
+ </ul>
+ Use -mxxx or -mno-xxx will enable or disable those extersions.
+ for example: Using <code>-mloongson-mmi</code>/<code>-mno-loongson-mmi</code>
+ will enable/disable Loongson MultiMedia Instructions extensions.
+ <li>
+ Support has been added for the following processors
+ (GCC identifiers in parentheses):
+ <ul>
+ <li>Loongson 3A1000 (<code>gs464</code>)
+ which default enable <code>loongson-mmi</code>, <code>loongson-ext</code>.</li>
+ <li>Loongson 3A2000/3A3000 (<code>gs464e</code>)
+ which default enable <code>loongson-mmi</code>, <code>loongson-ext</code>, <code>loongson-ext2</code>.</li>
+ <li>Loongson 2K1000 (<code>gs264e</code>)
+ which default enable <code>loongson-ext</code>, <code>loongson-ext2</code>, <code>msa</code>.</li>
+ </ul>
+ The GCC identifiers can be used
+ as arguments to the <code>-mcpu</code> or <code>-mtune</code> options,
+ for example: <code>-mcpu=gs464</code> or
+ <code>-mtune=gs464e</code> or as arguments to the equivalent target
+ attributes and pragmas.
+ </li>
+</ul>
+
<!-- <h3 id="hsa">Heterogeneous Systems Architecture</h3> -->
<!-- <h3 id="x86">IA-32/x86-64</h3> -->
next reply other threads:[~2018-12-31 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 12:32 Paul Hua [this message]
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
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=CAKjxQHkbwOD2pgu-gHdYgri-TSqmMGc-GNCB2aXSOh3dtfVVMA@mail.gmail.com \
--to=paul.hua.gm@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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).