bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/24311] ld 2.31+ (powerpc64-linux-musl) test suite: FAIL: S-recor


From: cvs-commit at gcc dot gnu.org
Subject: [Bug ld/24311] ld 2.31+ (powerpc64-linux-musl) test suite: FAIL: S-records with constructors
Date: Fri, 08 Mar 2019 12:59:26 +0000

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

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
The master branch has been updated by Alan Modra <address@hidden>:

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

commit ebd2263ba9a9124d93bbc0ece63d7e0fae89b40e
Author: Alan Modra <address@hidden>
Date:   Fri Mar 8 22:41:55 2019 +1030

    PR24311, FAIL: S-records with constructors

    Not padding string merge section output to its alignment can cause
    failures of the S-record tests when input string merge sections are
    padded, since the ELF linker output for the single string section
    would shrink compared to the SREC linker output.  That might result in
    following sections having different addresses.
    On the other hand, padding string merge section output when input
    string merge sections are *not* padded can also cause failures, in
    this case due to the ELF linker output for the string section being
    larger (due to padding) than the SREC linker output.

    It would be better to write a more robust test, but it is also nice
    to leave input unchanged when no string merges occur.

        PR 24311
        * merge.c (merge_strings): Return secinfo.  Don't pad section
        to alignment here.
        (_bfd_merge_sections): Pad section to alignment here, if input
        sections contributing to merged output all pad to alignment.
        Formatting.

-- 
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]