[llvm] [BOLT][AArch64] Handle OpNegateRAState to enable optimizing binaries with pac-ret hardening (PR #120064)
Paschalis Mpeis via llvm-commits
llvm-commits at lists.llvm.org
Wed Sep 24 01:47:17 PDT 2025
Gergely =?utf-8?q?Bálint?= <balintgergely99 at gmail.com>,Gergely Balint
<gergely.balint at arm.com>,Gergely Balint <gergely.balint at arm.com>
Message-ID:
In-Reply-To: <llvm.org/llvm/llvm-project/pull/120064 at github.com>
paschalis-mpeis wrote:
> But now I realize that Stubs inserted in LongJmp are tricky, because two calls to the same target can share a Stub, but they might come from ranges with opposing RAStates, in which case the Stub's state is not clear.
How would the current implementation handle this?
Detect the inconsistent state and ignore the 2nd function (ie, the one that tried to reuse a stub that was in a wrong state) ?
https://github.com/llvm/llvm-project/pull/120064
More information about the llvm-commits
mailing list