summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorMatthias Kaehlcke <mka@chromium.org>2017-06-21 16:28:05 -0700
committerGreg Hackmann <ghackmann@google.com>2017-10-09 14:00:13 -0700
commit6613aeae39d692d5a1f0432b76184b7ef84b4072 (patch)
tree4aec0dc8a371da2b7b9a4a59d91b4b00b391cc83 /tools/perf/scripts/python
parent203bd5f980384f6c5449191a42865950e5d86b3a (diff)
UPSTREAM: 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> (cherry picked commit d77698df39a512911586834d303275ea5fda74d0) Signed-off-by: Greg Hackmann <ghackmann@google.com> Change-Id: I4283d10c6fe31cf194b35adc5371732b89eb3ae3
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions