[Top][All Lists]

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

[Bug gold/20442] R_SPARC_GOTDATA_OP_LOX10 incorrectly falls back on R_SP

From: cvs-commit at gcc dot gnu.org
Subject: [Bug gold/20442] R_SPARC_GOTDATA_OP_LOX10 incorrectly falls back on R_SPARC_GOT13
Date: Wed, 10 Aug 2016 18:11:56 +0000


--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
The binutils-2_27-branch branch has been updated by Cary Coutant


commit 652f9c564865f6593c288bdae87944cca4cebdc4
Author: James Clarke <address@hidden>
Date:   Wed Aug 10 09:47:45 2016 -0700

    Fix improper handling of R_SPARC_GOTDATA_OP_LOX10 relocation.

    The fall-through in Target_sparc::Relocate::relocate for
    R_SPARC_GOTDATA_OP_LOX10 is currently R_SPARC_GOT13, but should
    clearly be R_SPARC_GOT10. GCC has been seen to emit a sethi/xor
    rather than a sethi/or sequence to load a 32-bit immediate, but
    if R_SPARC_GOT13 is used then bits 10-12 get zeroed out as both
    the sethi and xor immediates contain them.

        PR gold/20442
        * sparc.cc (Target_sparc::Relocate::relocate): R_SPARC_GOTDATA_OP_LOX10
        should fall back on R_SPARC_GOT10, not R_SPARC_GOT13.

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]