Hi,
-moverride is not a feature modifier, so it is currently misplaced in the
documentation.
Fix that by moving it out to the general AArch64 options section.
Checked in the HTML output that is now in a sensible place, and committed
as attached as obvious as revision 225384.
Thanks,
James
---
2015-07-03 James Greenhalgh <james.greenha...@arm.com>
* doc/invoke.texi (moverride): Move to correct section.
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 844d7edaecf2bc6642324ad8513f7c2add0ee486..1dfce1143027cef86d8fbf59580035e6d25f1189 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -12496,6 +12496,15 @@ the target processor for which to tune for performance (as if
by @option{-mtune}). Where this option is used in conjunction
with @option{-march} or @option{-mtune}, those options take precedence
over the appropriate part of this option.
+
+@item -moverride=@var{string}
+@opindex moverride
+Override tuning decisions made by the back-end in response to a
+@option{-mtune=} switch. The syntax, semantics, and accepted values
+for @var{string} in this option are not guaranteed to be consistent
+across releases.
+
+This option is only intended to be useful when developing GCC.
@end table
@subsubsection @option{-march} and @option{-mcpu} Feature Modifiers
@@ -12526,14 +12535,6 @@ Enable Limited Ordering Regions support.
@item rdma
Enable ARMv8.1 Advanced SIMD instructions.
-@item -moverride=@var{string}
-@opindex master
-Override tuning decisions made by the back-end in response to a
-@option{-mtune=} switch. The syntax, semantics, and accepted values
-for @var{string} in this option are not guaranteed to be consistent
-across releases.
-
-This option is only intended to be useful when developing GCC.
@end table
That is, @option{crypto} implies @option{simd} implies @option{fp}.
