Hi all,

Here's a wwwdocs patch mentioning the recently-added support for the Arm Neoverse N1 and Neoverse E1 processors.
Checked the output on Firefox.

Ok to commit (from an aarch64 perspective)?

Thanks,
Kyrill

Index: htdocs/gcc-9/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-9/changes.html,v
retrieving revision 1.43
diff -U 3 -r1.43 changes.html
--- htdocs/gcc-9/changes.html	21 Feb 2019 10:32:55 -0000	1.43
+++ htdocs/gcc-9/changes.html	22 Feb 2019 09:04:53 -0000
@@ -267,6 +267,7 @@
     <ul>
 	<li>Arm Cortex-A76 (<code>cortex-a76</code>).</li>
 	<li>Arm Cortex-A55/Cortex-A76 DynamIQ big.LITTLE (<code>cortex-a76.cortex-a55</code>).</li>
+	<li>Arm Neoverse N1 (<code>neoverse-n1</code>).</li>
     </ul>
     The GCC identifiers can be used
     as arguments to the <code>-mcpu</code> or <code>-mtune</code> options,
@@ -288,6 +289,10 @@
 <h5 id="aarch64">AArch64 specific</h5>
 <ul>
   <li>
+    Support has been added for the Arm Neoverse E1 processor (<code>-mcpu=neoverse-e1</code>)
+  </li>
+
+  <li>
     The AArch64 port now has support for stack clash protection using the
     <a href="https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html#index-fstack-protector";><code>-fstack-clash-protection</code></a> option.  The probing interval/guard
     size can be set by using <code>--param stack-clash-protection-guard-size=12|16</code>.

Reply via email to