mirrors/gcc
0
0
Fork 0
mirror of https://gcc.gnu.org/git/gcc.git synced 2024-11-27 22:03:57 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

[aarch64] Document rewriting of -march=native to -mcpu=native

Browse Source 
Commit dd9e5f4db2 changed -march=native to
treat it as -mcpu=native if no other mcpu or mtune option was given.
It would make sense to document this, especially if we try to persuade
compilers like LLVM to take the same approach.
This patch documents that behaviour.

Bootstrapped and tested on aarch64-none-linux-gnu.

Signed-off-by: Kyrylo Tkachov <ktkachov@nvidia.com>

gcc/ChangeLog:

	* doc/invoke.texi (AArch64 Options): Document rewriting of
	-march=native to -mcpu=native.
This commit is contained in:
Kyrylo Tkachov 2024-07-16 16:59:42 +05:30
parent 228972b2b7
commit a2cb656c0d
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/doc/invoke.texi
View File

@ -21498,7 +21498,10 @@ and the features that they enable by default:
The value @samp{native} is available on native AArch64 GNU/Linux and
causes the compiler to pick the architecture of the host system. This
option has no effect if the compiler is unable to recognize the
architecture of the host system,
architecture of the host system. When @option{-march=native} is given and
no other @option{-mcpu} or @option{-mtune} is given then GCC will pick
the host CPU as the CPU to tune for as well as select the architecture features
from. That is, @option{-march=native} is treated as @option{-mcpu=native}.
The permissible values for @var{feature} are listed in the sub-section
on @ref{aarch64-feature-modifiers,,@option{-march} and @option{-mcpu}