summaryrefslogtreecommitdiffstats
path: root/drivers/leds/leds-max77693.c
diff options
context:
space:
mode:
authorMatthias Kaehlcke <mka@chromium.org>2017-06-21 16:28:05 -0700
committerMasahiro Yamada <yamada.masahiro@socionext.com>2017-06-25 12:56:52 +0900
commitd77698df39a512911586834d303275ea5fda74d0 (patch)
tree308192621eece4e013a58d7da9a6d93262963788 /drivers/leds/leds-max77693.c
parent032a2c4f65a2f81c93e161a11197ba19bc14a909 (diff)
downloadop-kernel-dev-d77698df39a512911586834d303275ea5fda74d0.zip
op-kernel-dev-d77698df39a512911586834d303275ea5fda74d0.tar.gz
x86/build: Specify stack alignment for clang
For gcc stack alignment is configured with -mpreferred-stack-boundary=N, clang has the option -mstack-alignment=N for that purpose. Use the same alignment as with gcc. If the alignment is not specified clang assumes an alignment of 16 bytes, as required by the standard ABI. However as mentioned in d9b0cde91c60 ("x86-64, gcc: Use -mpreferred-stack-boundary=3 if supported") the standard kernel entry on x86-64 leaves the stack on an 8-byte boundary, as a consequence clang will keep the stack misaligned. Signed-off-by: Matthias Kaehlcke <mka@chromium.org> Acked-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'drivers/leds/leds-max77693.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud