summaryrefslogtreecommitdiff
path: root/arch/mips/crypto
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2021-05-08 01:07:51 +0300
committerArnd Bergmann <arnd@arndb.de>2021-05-10 18:50:47 +0300
commit0652035a57945e14e611dafae2ec5b46a05bc1d1 (patch)
tree0c34544a7755bc1ee0a822e86458d3ed9215533f /arch/mips/crypto
parentf12d3ff3f41cc92f67cfaf29697685e8834fe4a4 (diff)
downloadlinux-0652035a57945e14e611dafae2ec5b46a05bc1d1.tar.xz
asm-generic: unaligned: remove byteshift helpers
In theory, compilers should be able to work this out themselves so we can use a simpler version based on the swab() helpers. I have verified that this works on all supported compiler versions (gcc-4.9 and up, clang-10 and up). Looking at the object code produced by gcc-11, I found that the impact is mostly a change in inlining decisions that lead to slightly larger code. In other cases, this version produces explicit byte swaps in place of separate byte access, or comparing against pre-swapped constants. While the source code is clearly simpler, I have not seen an indication of the new version actually producing better code on Arm, so maybe we want to skip this after all. From what I can tell, gcc recognizes the byteswap pattern in the byteshift.h header and can turn it into explicit instructions, but it does not turn a __builtin_bswap32() back into individual bytes when that would result in better output, e.g. when storing a byte-reversed constant. Suggested-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'arch/mips/crypto')
0 files changed, 0 insertions, 0 deletions