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 <ger...@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...@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> -->