2013-05-15 15:02:12 +00:00
|
|
|
|
|
|
|
|
# RUN: llvm-mc -triple powerpc64-unknown-unknown -filetype=obj %s | \
|
|
|
|
|
# RUN: llvm-readobj -s -sd | FileCheck %s
|
|
|
|
|
|
|
|
|
|
# This checks that fixups that can be resolved within the same
|
|
|
|
|
# object file are applied correctly.
|
|
|
|
|
|
[PowerPC] Fix processing of ha16/lo16 fixups
The current PowerPC MC back end distinguishes between fixup_ppc_ha16
and fixup_ppc_lo16, which are determined by the instruction the fixup
applies to, and uses this distinction to decide whether a fixup ought
to resolve to the high or the low part of a symbol address.
This isn't quite correct, however. It is valid -if unusual- assembler
to use, e.g.
li 1, symbol@ha
or
lis 1, symbol@l
Whether the high or the low part of the address is used depends solely
on the @ suffix, not on the instruction.
In addition, both
li 1, symbol
and
lis 1, symbol
are valid, assuming the symbol address fits into 16 bits; again, both
will then refer to the actual symbol value (so li will load the value
itself, while lis will load the value shifted by 16).
To fix this, two places need to be adapted. If the fixup cannot be
resolved at assembler time, a relocation needs to be emitted via
PPCELFObjectWriter::getRelocType. This routine already looks at
the VK_ type to determine the relocation. The only problem is that
will reject any _LO modifier in a ha16 fixup and vice versa. This
is simply incorrect; any of those modifiers ought to be accepted
for either fixup type.
If the fixup *can* be resolved at assembler time, adjustFixupValue
currently selects the high bits of the symbol value if the fixup
type is ha16. Again, this is incorrect; see the above example
lis 1, symbol
Now, in theory we'd have to respect a VK_ modifier here. However,
in fact common code never even attempts to resolve symbol references
using any nontrivial VK_ modifier at assembler time; it will always
fall back to emitting a reloc and letting the linker handle it.
If this ever changes, presumably there'd have to be a target callback
to resolve VK_ modifiers. We'd then have to handle @ha etc. there.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@182091 91177308-0d34-0410-b5e6-96231b3b80d8
2013-05-17 12:36:29 +00:00
|
|
|
.text
|
|
|
|
|
|
|
|
|
|
addi 1, 1, target
|
|
|
|
|
addis 1, 1, target
|
|
|
|
|
|
|
|
|
|
.set target, 0x1234
|
|
|
|
|
|
2013-05-15 15:02:12 +00:00
|
|
|
.data
|
|
|
|
|
|
|
|
|
|
.quad v1
|
|
|
|
|
.word v2
|
|
|
|
|
.short v3
|
|
|
|
|
.byte v4
|
|
|
|
|
|
|
|
|
|
.set v1, 0x123456789abcdef0
|
|
|
|
|
.set v2, 0x87654321
|
|
|
|
|
.set v3, 0xbeef
|
|
|
|
|
.set v4, 0x42
|
|
|
|
|
|
[PowerPC] Fix processing of ha16/lo16 fixups
The current PowerPC MC back end distinguishes between fixup_ppc_ha16
and fixup_ppc_lo16, which are determined by the instruction the fixup
applies to, and uses this distinction to decide whether a fixup ought
to resolve to the high or the low part of a symbol address.
This isn't quite correct, however. It is valid -if unusual- assembler
to use, e.g.
li 1, symbol@ha
or
lis 1, symbol@l
Whether the high or the low part of the address is used depends solely
on the @ suffix, not on the instruction.
In addition, both
li 1, symbol
and
lis 1, symbol
are valid, assuming the symbol address fits into 16 bits; again, both
will then refer to the actual symbol value (so li will load the value
itself, while lis will load the value shifted by 16).
To fix this, two places need to be adapted. If the fixup cannot be
resolved at assembler time, a relocation needs to be emitted via
PPCELFObjectWriter::getRelocType. This routine already looks at
the VK_ type to determine the relocation. The only problem is that
will reject any _LO modifier in a ha16 fixup and vice versa. This
is simply incorrect; any of those modifiers ought to be accepted
for either fixup type.
If the fixup *can* be resolved at assembler time, adjustFixupValue
currently selects the high bits of the symbol value if the fixup
type is ha16. Again, this is incorrect; see the above example
lis 1, symbol
Now, in theory we'd have to respect a VK_ modifier here. However,
in fact common code never even attempts to resolve symbol references
using any nontrivial VK_ modifier at assembler time; it will always
fall back to emitting a reloc and letting the linker handle it.
If this ever changes, presumably there'd have to be a target callback
to resolve VK_ modifiers. We'd then have to handle @ha etc. there.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@182091 91177308-0d34-0410-b5e6-96231b3b80d8
2013-05-17 12:36:29 +00:00
|
|
|
# CHECK: Section {
|
|
|
|
|
# CHECK: Name: .text
|
|
|
|
|
# CHECK-NEXT: Type: SHT_PROGBITS
|
|
|
|
|
# CHECK-NEXT: Flags [
|
|
|
|
|
# CHECK-NEXT: SHF_ALLOC
|
|
|
|
|
# CHECK-NEXT: SHF_EXECINSTR
|
|
|
|
|
# CHECK-NEXT: ]
|
|
|
|
|
# CHECK-NEXT: Address: 0x0
|
|
|
|
|
# CHECK-NEXT: Offset:
|
|
|
|
|
# CHECK-NEXT: Size: 8
|
|
|
|
|
# CHECK-NEXT: Link: 0
|
|
|
|
|
# CHECK-NEXT: Info: 0
|
|
|
|
|
# CHECK-NEXT: AddressAlignment: 4
|
|
|
|
|
# CHECK-NEXT: EntrySize: 0
|
|
|
|
|
# CHECK-NEXT: SectionData (
|
|
|
|
|
# CHECK-NEXT: 0000: 38211234 3C211234
|
|
|
|
|
# CHECK-NEXT: )
|
|
|
|
|
# CHECK-NEXT: }
|
|
|
|
|
|
2013-05-15 15:02:12 +00:00
|
|
|
# CHECK: Section {
|
|
|
|
|
# CHECK: Name: .data
|
|
|
|
|
# CHECK-NEXT: Type: SHT_PROGBITS
|
|
|
|
|
# CHECK-NEXT: Flags [
|
|
|
|
|
# CHECK-NEXT: SHF_ALLOC
|
|
|
|
|
# CHECK-NEXT: SHF_WRITE
|
|
|
|
|
# CHECK-NEXT: ]
|
|
|
|
|
# CHECK-NEXT: Address: 0x0
|
|
|
|
|
# CHECK-NEXT: Offset:
|
|
|
|
|
# CHECK-NEXT: Size: 15
|
|
|
|
|
# CHECK-NEXT: Link: 0
|
|
|
|
|
# CHECK-NEXT: Info: 0
|
|
|
|
|
# CHECK-NEXT: AddressAlignment: 4
|
|
|
|
|
# CHECK-NEXT: EntrySize: 0
|
|
|
|
|
# CHECK-NEXT: SectionData (
|
|
|
|
|
# CHECK-NEXT: 0000: 12345678 9ABCDEF0 87654321 BEEF42
|
|
|
|
|
# CHECK-NEXT: )
|
|
|
|
|
# CHECK-NEXT: }
|
|
|
|
|
|