[PATCH][wwwdocs] Mention native CPU detection in aarch64 notes for GCC 6

[PATCH][wwwdocs] Mention native CPU detection in aarch64 notes for GCC 6

[Kyrill Tkachov]

[-- Attachment #1: Type: text/plain, Size: 341 bytes --]

Hi all,

This patch adds a mention of the new native cpu detection feature in aarch64 GNU/Linux.
Gerald, this is a patch against htdocs/gcc-6/changes.html and I thought I had seen the 'changes' link
in gcc.gnu.org earlier but I don't see it now (there's only a release criteria link).
Is this a bug?

Ok to apply?

Thanks,
Kyrill

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: wwwdocs-aarch64-native.patch --]
[-- Type: text/x-patch; name=wwwdocs-aarch64-native.patch, Size: 1169 bytes --]

Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-6/changes.html,v
retrieving revision 1.7
diff -U 3 -r1.7 changes.html
--- changes.html	14 May 2015 22:07:28 -0000	1.7
+++ changes.html	19 May 2015 10:11:57 -0000
@@ -66,10 +66,19 @@
 
 
 <!-- .................................................................. -->
-<!-- <h2 id="targets">New Targets and Target Specific Improvements</h2> -->
-
-<!-- <h3 id="aarch64">AArch64</h3> -->
+<h2 id="targets">New Targets and Target Specific Improvements</h2>
 
+<h3 id="aarch64">AArch64</h3>
+   <ul>
+     <li>
+       The new command line options <code>-march=native</code>,
+       <code>-mcpu=native</code> and <code>-mtune=native</code> are now
+       available on native AArch64 GNU/Linux systems.  Specifying
+       these options will cause GCC to auto-detect the host CPU and
+       rewrite these options to the optimal setting for that system.
+       If GCC is unable to detect the host CPU these options have no effect.
+     </li>
+   </ul>
 <!-- <h3 id="arm">ARM</h3> -->
 
 <!-- <h3 id="avr">AVR</h3> -->

Re: [PATCH][wwwdocs] Mention native CPU detection in aarch64 notes for GCC 6

[James Greenhalgh]

On Tue, May 19, 2015 at 11:12:55AM +0100, Kyrill Tkachov wrote:
> Hi all,
> 
> This patch adds a mention of the new native cpu detection feature in aarch64
> GNU/Linux.  Gerald, this is a patch against htdocs/gcc-6/changes.html and I
> thought I had seen the 'changes' link in gcc.gnu.org earlier but I don't see
> it now (there's only a release criteria link).  Is this a bug?

Submit a patch?

> Ok to apply?

I think I remember Gerald saying in the past that it is within the
remit of port maintainers/reviewers to OK these, but be ready to revert or
update it if I am wrong!

This is fine to apply.

Thanks,
James

> Index: changes.html
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-6/changes.html,v
> retrieving revision 1.7
> diff -U 3 -r1.7 changes.html
> --- changes.html	14 May 2015 22:07:28 -0000	1.7
> +++ changes.html	19 May 2015 10:11:57 -0000
> @@ -66,10 +66,19 @@
>  
>  
>  <!-- .................................................................. -->
> -<!-- <h2 id="targets">New Targets and Target Specific Improvements</h2> -->
> -
> -<!-- <h3 id="aarch64">AArch64</h3> -->
> +<h2 id="targets">New Targets and Target Specific Improvements</h2>
>  
> +<h3 id="aarch64">AArch64</h3>
> +   <ul>
> +     <li>
> +       The new command line options <code>-march=native</code>,
> +       <code>-mcpu=native</code> and <code>-mtune=native</code> are now
> +       available on native AArch64 GNU/Linux systems.  Specifying
> +       these options will cause GCC to auto-detect the host CPU and
> +       rewrite these options to the optimal setting for that system.
> +       If GCC is unable to detect the host CPU these options have no effect.
> +     </li>
> +   </ul>
>  <!-- <h3 id="arm">ARM</h3> -->
>  
>  <!-- <h3 id="avr">AVR</h3> -->

Re: [PATCH][wwwdocs] Mention native CPU detection in aarch64 notes for GCC 6

[Gerald Pfeifer]

On Tue, 26 May 2015, James Greenhalgh wrote:
> I think I remember Gerald saying in the past that it is within the
> remit of port maintainers/reviewers to OK these, but be ready to 
> revert or update it if I am wrong!

You were (and are) very much quite right, James. :-)

(And given that Gerald is not always able to respond as quickly as 
he'd like, this mail being a "nice" example, this just makes sense.)

Gerald