[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <170914663626.3370652.5443900457103339584.b4-ty@arm.com>
Date: Wed, 28 Feb 2024 18:58:34 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Will Deacon <will@...nel.org>,
Stephen Boyd <swboyd@...omium.org>
Cc: linux-kernel@...r.kernel.org,
patches@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org,
Jason Ling <jasonling@...omium.org>,
Florian Fainelli <f.fainelli@...il.com>,
Mark Rutland <mark.rutland@....com>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Bill Wendling <morbo@...gle.com>,
Justin Stitt <justinstitt@...gle.com>,
llvm@...ts.linux.dev
Subject: Re: [PATCH] arm64: ftrace: Don't forbid CALL_OPS+CC_OPTIMIZE_FOR_SIZE with Clang
On Thu, 22 Feb 2024 22:40:29 -0800, Stephen Boyd wrote:
> 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.
>
> [...]
Applied to arm64 (for-next/misc), thanks!
[1/1] arm64: ftrace: Don't forbid CALL_OPS+CC_OPTIMIZE_FOR_SIZE with Clang
https://git.kernel.org/arm64/c/a743f26d03a9
--
Catalin
Powered by blists - more mailing lists