From: Thomas Preud'homme Date: Tue, 20 Feb 2018 12:48:50 +0000 (+0000) Subject: Clarify .arch_extension possible values X-Git-Tag: binutils-2_31~1259 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=8811c8f495557bb05a65d2c09eb529e2675b6a57;p=external%2Fbinutils.git 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 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 bb827aa..19fb02f 100644 --- a/gas/ChangeLog +++ b/gas/ChangeLog @@ -1,3 +1,8 @@ +2018-02-20 Thomas Preud'homme + + * doc/c-arm.texi (.arch_extension): Mention extensions it accepts are + also the same as -march. + 2018-02-17 H.J. Lu * NEWS: Mention .nop directive. diff --git a/gas/doc/c-arm.texi b/gas/doc/c-arm.texi index ec0f544..f67696f 100644 --- 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.