diff options
author | Nicolas Pitre <nicolas.pitre@linaro.org> | 2017-11-29 07:52:52 +0100 |
---|---|---|
committer | Russell King <rmk+kernel@armlinux.org.uk> | 2017-12-17 22:14:21 +0000 |
commit | 75fea300d73ae5b18957949a53ec770daaeb6fc2 (patch) | |
tree | 9e07e50f5b8992512603774358e0979906237a59 /crypto/ansi_cprng.c | |
parent | 55e7cff44c7c322310aded74ed92c54b22ccccd4 (diff) | |
download | linux-75fea300d73ae5b18957949a53ec770daaeb6fc2.tar.gz linux-75fea300d73ae5b18957949a53ec770daaeb6fc2.tar.bz2 linux-75fea300d73ae5b18957949a53ec770daaeb6fc2.zip |
ARM: 8723/2: always assume the "unified" syntax for assembly code
The GNU assembler has implemented the "unified syntax" parsing since
2005. This "unified" syntax is required when the kernel is built in
Thumb2 mode. However the "unified" syntax is a mixed bag of features,
including not requiring a `#' prefix with immediate operands. This leads
to situations where some code builds just fine in Thumb2 mode and fails
to build in ARM mode if that prefix is missing. This behavior
discrepancy makes build tests less valuable, forcing both ARM and Thumb2
builds for proper coverage.
Let's "fix" this issue by always using the "unified" syntax for both ARM
and Thumb2 mode. Given that the documented minimum binutils version that
properly builds the kernel is version 2.20 released in 2010, we can
assume that any toolchain capable of building the latest kernel is also
"unified syntax" capable.
Whith this, a bunch of macros used to mask some differences between both
syntaxes can be removed, with the side effect of making LTO easier.
Suggested-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Nicolas Pitre <nico@linaro.org>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Diffstat (limited to 'crypto/ansi_cprng.c')
0 files changed, 0 insertions, 0 deletions