bug-binutils
[Top][All Lists]
Advanced

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

[Bug binutils/22875] Strip complains about and then destroys unrecognise


From: cvs-commit at gcc dot gnu.org
Subject: [Bug binutils/22875] Strip complains about and then destroys unrecognised relocs
Date: Wed, 04 Apr 2018 01:03:21 +0000

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

--- Comment #9 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
The master branch has been updated by Maciej W. Rozycki <address@hidden>:

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

commit 5d7c8b80485d75242e7c78e79b3ecb4c71abaee3
Author: Maciej W. Rozycki <address@hidden>
Date:   Wed Apr 4 02:00:49 2018 +0100

    PR binutils/22875: i860/ELF: Report unsupported relocation types

    Complement commit f3185997ac09 ("PR 22875: Stop strip corrupting unknown
    relocs"), <https://sourceware.org/ml/binutils/2018-02/msg00445.html>,
    and also set the `bfd_error_bad_value' error and report an unsupported
    relocation type if a howto lookup fails with the i860 backend, fixing a
    confusing `no error' error message and removing a binutils test failure:

    failed with: <.../binutils/strip-new: tmpdir/bintest.o: no error>,
expected: <.* bad value>
    .../binutils/strip-new: tmpdir/bintest.o: no error
    FAIL: binutils-all/strip-13

    with the `i860-stardent-elf' target.

        bfd/
        * elf32-i860.c (lookup_howto): Add `abfd' parameter.  Set the
        `bfd_error_bad_value' error and call `_bfd_error_handler' on a
        howto lookup failure.
        (elf32_i860_reloc_type_lookup): Adjust `lookup_howto' call
        accordingly.
        (elf32_i860_info_to_howto_rela): Likewise.
        (elf32_i860_relocate_splitn): Likewise.
        (elf32_i860_relocate_pc16): Likewise.
        (elf32_i860_relocate_pc26): Likewise.
        (elf32_i860_relocate_section): Likewise.

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