Documentation for .arch and .cpu directives currently says that it
accepts the same name as -march/-mcpu command-line options respectively.
However it only accept the architecture/CPU part of those options: it
does not accept specifying an extension which is done via
.arch_extension. This patch clarifies that the extension is not
accepted.
2018-07-25 Thomas Preud'homme <thomas.preudhomme@linaro.org>
gas/
* doc/c-arm.texi (.arch directive): Clarify that name must not include
an extension.
(.cpu directive): Likewise.
+2018-07-25 Thomas Preud'homme <thomas.preudhomme@linaro.org>
+
+ * doc/c-arm.texi (.arch directive): Clarify that name must not include
+ an extension.
+ (.cpu directive): Likewise.
+
2018-07-24 H.J. Lu <hongjiu.lu@intel.com>
* config/tc-i386.c (build_vex_prefix): Use unsigned int to
@cindex @code{.arch} directive, ARM
@item .arch @var{name}
Select the target architecture. Valid values for @var{name} are the same as
-for the @option{-march} command-line option.
+for the @option{-march} command-line option without the instruction set
+extension.
Specifying @code{.arch} clears any previously selected architecture
extensions.
@cindex @code{.cpu} directive, ARM
@item .cpu @var{name}
Select the target processor. Valid values for @var{name} are the same as
-for the @option{-mcpu} command-line option.
+for the @option{-mcpu} command-line option without the instruction set
+extension.
Specifying @code{.cpu} clears any previously selected architecture
extensions.