Clarify .arch_extension possible values

Documentation for .arch_extension says it accepts the same architectural
extensions as those accepted by -mcpu. Given the name and the fact that
-march for obvious reason also accept the same extensions, I believe
it's worth mentioning that it accepts the same extensions as both
-march and -mcpu. This commit addresses that.

2018-02-20  Thomas Preud'homme  <thomas.preudhomme@arm.com>

gas/
	* doc/c-arm.texi (.arch_extension): Mention extensions it accepts are
	also the same as -march.

diff --git a/gas/ChangeLog b/gas/ChangeLog
index bb827aa280f1a7754e94a988e9677d0c1dfc79bd..19fb02f7dee8345b0c52de7841bf199b165b4175 100644 (file)
--- a/gas/ChangeLog
+++ b/gas/ChangeLog
@@ -1,3 +1,8 @@
+2018-02-20  Thomas Preud'homme  <thomas.preudhomme@arm.com>
+
+       * doc/c-arm.texi (.arch_extension): Mention extensions it accepts are
+       also the same as -march.
+
 2018-02-17  H.J. Lu  <hongjiu.lu@intel.com>
 
        * NEWS: Mention .nop directive.

diff --git a/gas/doc/c-arm.texi b/gas/doc/c-arm.texi
index ec0f544794353a8db75b14bc5d137bd19a4d8105..f67696f00fbbbf76627d41cf45b682432e272ba8 100644 (file)
--- a/gas/doc/c-arm.texi
+++ b/gas/doc/c-arm.texi
@@ -631,7 +631,7 @@ extensions.
 @item .arch_extension @var{name}
 Add or remove an architecture extension to the target architecture.  Valid
 values for @var{name} are the same as those accepted as architectural
-extensions by the @option{-mcpu} commandline option.
+extensions by the @option{-mcpu} and @option{-march} commandline options.
 
 @code{.arch_extension} may be used multiple times to add or remove extensions
 incrementally to the architecture being compiled for.