This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[PATCH, binutils/ARM] 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 patch addresses that.

ChangeLog entry is as follows:

*** gas/ChangeLog ***

2018-02-19  Thomas Preud'homme  <>

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

Testing: doc built and display fine.

Ok for master branch?

Best regards,

diff --git a/gas/doc/c-arm.texi b/gas/doc/c-arm.texi
index ec0f544794353a8db75b14bc5d137bd19a4d8105..f67696f00fbbbf76627d41cf45b682432e272ba8 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.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]