bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/32572] -z force-bti + -Ttext-segment produce wrong PLT entries o


From: cvs-commit at gcc dot gnu.org
Subject: [Bug ld/32572] -z force-bti + -Ttext-segment produce wrong PLT entries on aarch64
Date: Fri, 24 Jan 2025 14:59:23 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=32572

--- Comment #7 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The binutils-2_44-branch branch has been updated by Richard Earnshaw
<rearnsha@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a4e996833fe5d770a9efc95d35567b51025cf23f

commit a4e996833fe5d770a9efc95d35567b51025cf23f
Author: Richard Earnshaw <rearnsha@arm.com>
Date:   Thu Jan 23 10:53:54 2025 +0000

    aarch64: Fix PLT fixups when BTI is used [PR32572]

    PR ld/32572

    There are two problems addressed in this PR.  Firstly, the choice of
    whether or not a PLT stub needs a BTI on entry was too strict,
    resulting in non-pie executables not having a BTI on their stub.  But
    secondly, the logic to handle each stub types did not agree across the
    various places where this information is used.

    The first issue is fixed by using bfd_link_executable rather than
    bfd_link_pde.  The second is addressed by recording a delta for PLT
    stub alongside the stub itself.  This is then used without needing
    additional logic later on since it has been pre-calculated.

    A more comprehensive fix would involve creating a data structure to
    describe each fixup, including a call-back function to apply any
    relocations.  But that's a fairly large change and not appropriate for
    backporting.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]