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

Sam James <sam at gentoo dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |2.44
           See Also|                            |https://reviews.llvm.org/D2
                   |                            |2116

--- Comment #4 from Sam James <sam at gentoo dot org> ---
commit f4e363cae297ec3e24dec0d95f3d422879f498a3
Author: Hakan Candar <hakancan...@protonmail.com>
Date:   Mon Oct 28 11:01:59 2024 +0000

    ld/ELF: Add --image-base command line option to the ELF linker

    LLD has dropped the option -Ttext-segment for specifying image base
    addresses, instead forcing the use of the --image-base option for both
    ELF and PE targets. As it stands, GNU LD and LLVM LLD are incompatible,
    having two different options for the same functionality.

    This patch enables the use of --image-base on ELF targets, advancing
    consistency and compatibility.

    See: https://reviews.llvm.org/D70468
        
https://maskray.me/blog/2020-11-15-explain-gnu-linker-options#address-related
         https://sourceware.org/bugzilla/show_bug.cgi?id=25207

    Moreover, a new test has been added to ensure -z separate-code behaviour
    when used with -Ttext-segment stays the same. When this combination is
    used, -Ttext-segment sets the address of the first segment (R), not the
    text segment (RX), and like with -z noseparate-code, no segments lesser
    than the specified address are created. If this behaviour was to change,
    the first (R) segment of the ELF file would begin in a lesser address
    than the specified text (RX) segment, breaking traditional use of this
    option for specifying image base address.

All done for 2.44 I think. Please reopen if I'm mistaken.

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

Reply via email to