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

[cvs-commit at gcc dot gnu.org]

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

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

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

commit 007801eeb19ed565eb4dc4020831f6d293f46930
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.

    gold/
        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.