maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lld/test/ELF/mips-gprel32-relocs-gp0.s

49 lines
1.4 KiB
ArmAsm
Raw Normal View History

[ELF][MIPS] Set GP0 value to zero in case of relocatable object generation LLD does not update relocations addends when generate a relocatable object. That is why we should not write a non-zero GP0 value into the .reginfo and .MIPS.options sections. And we should not accept input object files with non-zero GP0 value because we cannot handle them properly. llvm-svn: 282716
2016-09-29 20:58:48 +08:00
# Check that relocatable object produced by LLD has zero gp0 value.
[ELF][MIPS] Do not accept non-zero GP0 value for relocatable object only Follow-up to r282716. Reject input files with non-zero GP0 value only in case of relocatable object generation. In other case we can handle arbitrary GP0 value so it does not have a sense to make the restriction so wide. llvm-svn: 283194
2016-10-04 16:24:25 +08:00
# Also check an error message if input object file has non-zero gp0 value
# and the linker generates a relocatable object.
[ELF][MIPS] Set GP0 value to zero in case of relocatable object generation LLD does not update relocations addends when generate a relocatable object. That is why we should not write a non-zero GP0 value into the .reginfo and .MIPS.options sections. And we should not accept input object files with non-zero GP0 value because we cannot handle them properly. llvm-svn: 282716
2016-09-29 20:58:48 +08:00
# mips-gp0-non-zero.o is a relocatable object produced from the asm code
# below and linked by GNU bfd linker.
[ELF][MIPS] Replace binary test input file by asembler code in the test. NFC llvm-svn: 276809
2016-07-27 05:11:34 +08:00
# RUN: llvm-mc -filetype=obj -triple=mips-unknown-linux %s -o %t.o
[ELF][MIPS] Do not accept non-zero GP0 value for relocatable object only Follow-up to r282716. Reject input files with non-zero GP0 value only in case of relocatable object generation. In other case we can handle arbitrary GP0 value so it does not have a sense to make the restriction so wide. llvm-svn: 283194
2016-10-04 16:24:25 +08:00
# RUN: ld.lld -r -o %t-rel.o %t.o
# RUN: llvm-readobj -mips-reginfo %t-rel.o | FileCheck --check-prefix=REL %s
# RUN: ld.lld -shared -o %t.so %S/Inputs/mips-gp0-non-zero.o
# RUN: llvm-readobj -mips-reginfo %t.so | FileCheck --check-prefix=DSO %s
[ELF][MIPS] Replace binary test input file by asembler code in the test. NFC llvm-svn: 276809
2016-07-27 05:11:34 +08:00
# RUN: llvm-objdump -s -t %t.so | FileCheck --check-prefix=DUMP %s
[ELF][MIPS] Do not accept non-zero GP0 value for relocatable object only Follow-up to r282716. Reject input files with non-zero GP0 value only in case of relocatable object generation. In other case we can handle arbitrary GP0 value so it does not have a sense to make the restriction so wide. llvm-svn: 283194
2016-10-04 16:24:25 +08:00
# RUN: not ld.lld -r -o %t-rel.o %S/Inputs/mips-gp0-non-zero.o 2>&1 \
[ELF][MIPS] Set GP0 value to zero in case of relocatable object generation LLD does not update relocations addends when generate a relocatable object. That is why we should not write a non-zero GP0 value into the .reginfo and .MIPS.options sections. And we should not accept input object files with non-zero GP0 value because we cannot handle them properly. llvm-svn: 282716
2016-09-29 20:58:48 +08:00
# RUN: | FileCheck --check-prefix=ERR %s
[ELF][MIPS] Replace binary test input file by asembler code in the test. NFC llvm-svn: 276809
2016-07-27 05:11:34 +08:00
# REQUIRES: mips
[ELF][MIPS] Do not accept non-zero GP0 value for relocatable object only Follow-up to r282716. Reject input files with non-zero GP0 value only in case of relocatable object generation. In other case we can handle arbitrary GP0 value so it does not have a sense to make the restriction so wide. llvm-svn: 283194
2016-10-04 16:24:25 +08:00
# REL: GP: 0x0
# DSO: GP: 0x27FF0
[ELF][MIPS] Replace binary test input file by asembler code in the test. NFC llvm-svn: 276809
2016-07-27 05:11:34 +08:00
# DUMP: Contents of section .rodata:
[ELF][MIPS] Exclude mips .got from PT_GNU_RELRO segment On MIPS .got section cannot be included into the PT_GNU_RELRO segment. Sometimes it might work, but in general it is unsupported. One of the problem is that all sections marked by SHF_MIPS_GPREL should be grouped together because data in these sections is addressable with a gp relative address, but such sections might be writable. This patch exclude mips .got from PT_GNU_RELRO segment and group SHF_MIPS_GPREL sections. llvm-svn: 292161
2017-01-17 05:17:23 +08:00
# DUMP: 00f4 ffff0004 ffff0008
[ELF][MIPS] Do not accept non-zero GP0 value for relocatable object only Follow-up to r282716. Reject input files with non-zero GP0 value only in case of relocatable object generation. In other case we can handle arbitrary GP0 value so it does not have a sense to make the restriction so wide. llvm-svn: 283194
2016-10-04 16:24:25 +08:00
# ^ 0x10004 + 0x7ff0 - 0x27ff0
# ^ 0x10008 + 0x7ff0 - 0x27ff0
[ELF][MIPS] Replace binary test input file by asembler code in the test. NFC llvm-svn: 276809
2016-07-27 05:11:34 +08:00
# DUMP: SYMBOL TABLE:
# DUMP: 00010008 .text 00000000 bar
# DUMP: 00010004 .text 00000000 foo
[ELF][MIPS] Make _gp, _gp_disp, __gnu_local_gp global symbols These MIPS specific symbols should be global because in general they can have an arbitrary value. By default this value is a fixed offset from .got section. This patch adds more checks to the mips-gp-local.s test case but marks it as XFAIL because LLD does not allow redefinition of absolute symbols value by a linker script. This should be fixed by D27276. Differential revision: https://reviews.llvm.org/D27524 llvm-svn: 289025
2016-12-08 14:19:47 +08:00
# DUMP: 00027ff0 *ABS* 00000000 .hidden _gp
[ELF][MIPS] Replace binary test input file by asembler code in the test. NFC llvm-svn: 276809
2016-07-27 05:11:34 +08:00
[ELF][MIPS] Convert .reginfo and .MIPS.options sections to synthetic input sections Previously, we have both input and output sections for .reginfo and .MIPS.options. Now for each such sections we have one synthetic input sections: MipsReginfoSection and MipsOptionsSection respectively. Both sections are handled as regular sections until the control reaches Writer. Writer then aggregates all sections whose type is SHT_MIPS_REGINFO or SHT_MIPS_OPTIONS to create a single synthesized input section. In that moment Writer also save GP0 value to the MipsGp0 field of the corresponding ObjectFile. This value required for R_MIPS_GPREL16 and R_MIPS_GPREL32 relocations calculation. Differential revision: https://reviews.llvm.org/D26444 llvm-svn: 286397
2016-11-10 05:36:56 +08:00
# ERR: error: {{.*}}mips-gp0-non-zero.o: unsupported non-zero ri_gp_value
[ELF][MIPS] Set GP0 value to zero in case of relocatable object generation LLD does not update relocations addends when generate a relocatable object. That is why we should not write a non-zero GP0 value into the .reginfo and .MIPS.options sections. And we should not accept input object files with non-zero GP0 value because we cannot handle them properly. llvm-svn: 282716
2016-09-29 20:58:48 +08:00
[ELF][MIPS] Replace binary test input file by asembler code in the test. NFC llvm-svn: 276809
2016-07-27 05:11:34 +08:00
.text
.global __start
__start:
lw $t0,%call16(__start)($gp)
foo:
nop
bar:
nop
.section .rodata, "a"
v:
.gpword foo
.gpword bar