forked from OSchip/llvm-project
[llvm-objdump] Correctly distinguish between the MachO upper/lower16 relocations
All other code in MachODump.cpp uses the same comparison, ((r_length & 0x1) == 1), for distinguishing between the two, while the code in llvm-objdump.cpp seemed to be incorrect. Differential Revision: https://reviews.llvm.org/D35240 llvm-svn: 307882
This commit is contained in:
parent
b244c2bafe
commit
fa5183b028
Binary file not shown.
|
@ -0,0 +1,4 @@
|
|||
RUN: llvm-objdump -r %p/Inputs/reloc-half.obj.macho-arm | FileCheck %s
|
||||
|
||||
CHECK-DAG: 00000004 ARM_RELOC_HALF :upper16:(_stringbuf)
|
||||
CHECK-DAG: 00000000 ARM_RELOC_HALF :lower16:(_stringbuf)
|
|
@ -1032,7 +1032,7 @@ static std::error_code getRelocationValueString(const MachOObjectFile *Obj,
|
|||
case MachO::ARM_RELOC_HALF_SECTDIFF: {
|
||||
// Half relocations steal a bit from the length field to encode
|
||||
// whether this is an upper16 or a lower16 relocation.
|
||||
bool isUpper = Obj->getAnyRelocationLength(RE) >> 1;
|
||||
bool isUpper = (Obj->getAnyRelocationLength(RE) & 0x1) == 1;
|
||||
|
||||
if (isUpper)
|
||||
fmt << ":upper16:(";
|
||||
|
|
Loading…
Reference in New Issue