https://sourceware.org/bugzilla/show_bug.cgi?id=30930
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #12 from Carlos O'Donell <carlos at redhat dot com> ---
I suggest starting by reverting the BTI stub change:
commit 15b4f66b0a9a3be6caf1898d22a13c39e662006f
Author: Szabolcs Nagy <szabolcs.n...@arm.com>
Date: Wed Jan 18 12:56:46 2023 +0000
bfd: aarch64: Fix stubs that may break BTI PR30076
Insert two stubs in a BTI enabled binary when fixing long calls: The
first is near the call site and uses an indirect jump like before,
but it targets the second stub that is near the call target site and
uses a direct jump.
This is needed when a single stub breaks BTI compatibility.
The stub layout is kept fixed between sizing and building the stubs,
so the location of the second stub is known at build time, this may
introduce padding between stubs when those are relaxed. Stub layout
with BTI disabled is unchanged.
... and see if that fixes the issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
