diff options
| author | Stephen Boyd <[email protected]> | 2024-02-23 06:40:29 +0000 |
|---|---|---|
| committer | Catalin Marinas <[email protected]> | 2024-02-28 15:16:37 +0000 |
| commit | a743f26d03a96593c0f3d05dc26b388f45de67c9 (patch) | |
| tree | b882297be2a0afcc93a9049af5965551b0659ea6 /scripts/generate_rust_target.rs | |
| parent | arm64/sme: Ensure that all fields in SMCR_EL1 are set to known values (diff) | |
| download | kernel-a743f26d03a96593c0f3d05dc26b388f45de67c9.tar.gz kernel-a743f26d03a96593c0f3d05dc26b388f45de67c9.zip | |
arm64: ftrace: Don't forbid CALL_OPS+CC_OPTIMIZE_FOR_SIZE with Clang
Per commit b3f11af9b2ce ("arm64: ftrace: forbid CALL_OPS with
CC_OPTIMIZE_FOR_SIZE"), GCC is silently ignoring `-falign-functions=N`
when passed `-Os`, causing functions to be improperly aligned. This
doesn't seem to be a problem with Clang though, where enabling CALL_OPS
with CC_OPTIMIZE_FOR_SIZE doesn't spit out any warnings at boot about
misaligned patch-sites. Only forbid CALL_OPS if GCC is used and we're
optimizing for size so that CALL_OPS can be used with clang optimizing
for size.
Cc: Jason Ling <[email protected]>
Cc: Florian Fainelli <[email protected]>
Cc: Mark Rutland <[email protected]>
Cc: Nathan Chancellor <[email protected]>
Cc: Nick Desaulniers <[email protected]>
Cc: Bill Wendling <[email protected]>
Cc: Justin Stitt <[email protected]>
Cc: [email protected]
Fixes: b3f11af9b2ce ("arm64: ftrace: forbid CALL_OPS with CC_OPTIMIZE_FOR_SIZE")
Signed-off-by: Stephen Boyd <[email protected]>
Reviewed-by: Nathan Chancellor <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Catalin Marinas <[email protected]>
Diffstat (limited to 'scripts/generate_rust_target.rs')
0 files changed, 0 insertions, 0 deletions
