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/ztext.s

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

46 lines
1.5 KiB
ArmAsm
Raw Normal View History

[ELF] - Implemented -znotext gold linker manual describes them as: -z text Do not permit relocations in read-only segments -z notext Permit relocations in read-only segments (default) In LLD default is to not permit them. Patch implements -z notext. Differential revision: https://reviews.llvm.org/D30530 llvm-svn: 297366
2017-03-09 16:48:34 +08:00
# REQUIRES: x86
# RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %s -o %t.o
Rename a test file and fix indentation. llvm-svn: 326504
2018-03-02 07:01:41 +08:00
# RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %p/Inputs/ztext.s -o %t2.o
[ELF][test] Make tests more tolerant to exact symbol addresses llvm-svn: 371588
2019-09-11 14:20:14 +08:00
# RUN: ld.lld %t2.o -o %t2.so -shared -soname=so
Add -z {combreloc,copyreloc,noexecstack,lazy,relro,text}. Differential Revision: https://reviews.llvm.org/D45902 llvm-svn: 330482
2018-04-21 05:24:08 +08:00
Don't create copy relocs or dummy plt's if given -z notext. Being passed -z notext is a pretty strong indication that the user is OK with text relocations. This is not the same behavior as bfd, but bfd defaults to -z notext, so it has to try to avoid text relocations and use them as a last resort. llvm-svn: 297789
2017-03-15 06:50:07 +08:00
# RUN: ld.lld -z notext %t.o %t2.so -o %t -shared
[test] Change llvm-readobj -long-option to --long-option or well-known short options. NFC Also change some options that have different semantics (cause confusion) in llvm-readelf mode: -s => -S -t => --symbols -sd => --section-data llvm-svn: 359651
2019-05-01 13:49:01 +08:00
# RUN: llvm-readobj --dynamic-table -r %t | FileCheck %s
Don't create copy relocs or dummy plt's if given -z notext. Being passed -z notext is a pretty strong indication that the user is OK with text relocations. This is not the same behavior as bfd, but bfd defaults to -z notext, so it has to try to avoid text relocations and use them as a last resort. llvm-svn: 297789
2017-03-15 06:50:07 +08:00
# RUN: ld.lld -z notext %t.o %t2.so -o %t2 -pie
[test] Change llvm-readobj -long-option to --long-option or well-known short options. NFC Also change some options that have different semantics (cause confusion) in llvm-readelf mode: -s => -S -t => --symbols -sd => --section-data llvm-svn: 359651
2019-05-01 13:49:01 +08:00
# RUN: llvm-readobj --dynamic-table -r %t2 | FileCheck %s
Don't create copy relocs or dummy plt's if given -z notext. Being passed -z notext is a pretty strong indication that the user is OK with text relocations. This is not the same behavior as bfd, but bfd defaults to -z notext, so it has to try to avoid text relocations and use them as a last resort. llvm-svn: 297789
2017-03-15 06:50:07 +08:00
# RUN: ld.lld -z notext %t.o %t2.so -o %t3
[test] Change llvm-readobj -long-option to --long-option or well-known short options. NFC Also change some options that have different semantics (cause confusion) in llvm-readelf mode: -s => -S -t => --symbols -sd => --section-data llvm-svn: 359651
2019-05-01 13:49:01 +08:00
# RUN: llvm-readobj --dynamic-table -r %t3 | FileCheck --check-prefix=STATIC %s
Don't create copy relocs or dummy plt's if given -z notext. Being passed -z notext is a pretty strong indication that the user is OK with text relocations. This is not the same behavior as bfd, but bfd defaults to -z notext, so it has to try to avoid text relocations and use them as a last resort. llvm-svn: 297789
2017-03-15 06:50:07 +08:00
[ELF][test] Change -o %t to -o /dev/null if the output is not needed
2020-02-13 13:48:45 +08:00
# RUN: not ld.lld %t.o %t2.so -o /dev/null -shared 2>&1 | FileCheck --check-prefix=ERR %s
# RUN: not ld.lld -z text %t.o %t2.so -o /dev/null -shared 2>&1 | FileCheck --check-prefix=ERR %s
[ELF] Remove -Wl,-z,notext hint The hint does not pull its weight: * adding -Wl,-z,notext often won't work (relocation types other than `symbolRel`, e.g. `R_AARCH64_LDST32_ABS_LO12_NC`) * for pure (no assembly) C/C++ projects, the "-fPIC" hint is sufficient
2021-11-01 03:10:42 +08:00
# ERR: error: relocation R_X86_64_64 cannot be used against symbol 'bar'; recompile with -fPIC
Add -z {combreloc,copyreloc,noexecstack,lazy,relro,text}. Differential Revision: https://reviews.llvm.org/D45902 llvm-svn: 330482
2018-04-21 05:24:08 +08:00
Don't create copy relocs or dummy plt's if given -z notext. Being passed -z notext is a pretty strong indication that the user is OK with text relocations. This is not the same behavior as bfd, but bfd defaults to -z notext, so it has to try to avoid text relocations and use them as a last resort. llvm-svn: 297789
2017-03-15 06:50:07 +08:00
# If the preference is to have text relocations, don't create plt of copy relocations.
[ELF] - Implemented -znotext gold linker manual describes them as: -z text Do not permit relocations in read-only segments -z notext Permit relocations in read-only segments (default) In LLD default is to not permit them. Patch implements -z notext. Differential revision: https://reviews.llvm.org/D30530 llvm-svn: 297366
2017-03-09 16:48:34 +08:00
[llvm-readelf] Make --all output order closer to GNU readelf https://bugs.llvm.org/show_bug.cgi?id=43403 The new order makes it easy to compare the two tools' --all. Reviewed By: grimar, rupprecht Differential Revision: https://reviews.llvm.org/D75592
2020-03-04 11:49:14 +08:00
# CHECK: DynamicSection [
# CHECK: FLAGS TEXTREL
# CHECK: TEXTREL 0x0
[ELF] - Implemented -znotext gold linker manual describes them as: -z text Do not permit relocations in read-only segments -z notext Permit relocations in read-only segments (default) In LLD default is to not permit them. Patch implements -z notext. Differential revision: https://reviews.llvm.org/D30530 llvm-svn: 297366
2017-03-09 16:48:34 +08:00
# CHECK: Relocations [
Rename a test file and fix indentation. llvm-svn: 326504
2018-03-02 07:01:41 +08:00
# CHECK-NEXT: Section {{.*}} .rela.dyn {
[ELF][X86] Allow PT_LOAD to have overlapping p_offset ranges on EM_X86_64 Port the D64906 technique to EM_X86_64. Differential Revision: https://reviews.llvm.org/D67482 llvm-svn: 371958
2019-09-16 15:05:34 +08:00
# CHECK-NEXT: 0x12A0 R_X86_64_RELATIVE - 0x12A0
# CHECK-NEXT: 0x12A8 R_X86_64_64 bar 0x0
# CHECK-NEXT: 0x12B0 R_X86_64_PC64 zed 0x0
Rename a test file and fix indentation. llvm-svn: 326504
2018-03-02 07:01:41 +08:00
# CHECK-NEXT: }
# CHECK-NEXT: ]
Set DF_TEXTREL to executables that need text relocations. Summary: If an executable needs text relocations, it should be marked as such so that the loader can prepare for text relocations. We currently create a dummy segment with DT_TEXTREL for that purpose. Generic ABI as of 2000 [1] mentioned that "Its [DT_TEXTREL's] use has been superseded by the DF_TEXTREL flag". However, it's actually not superseded even after 18 years. OpenBSD and musl recognize only DT_TEXTREL. So we still need to set both. [1] http://www.sco.com/developers/gabi/2000-07-17/ch5.dynamic.html Reviewers: rafael Subscribers: emaste, llvm-commits, arichardson Differential Revision: https://reviews.llvm.org/D43920 llvm-svn: 326503
2018-03-02 06:56:52 +08:00
[llvm-readelf] Make --all output order closer to GNU readelf https://bugs.llvm.org/show_bug.cgi?id=43403 The new order makes it easy to compare the two tools' --all. Reviewed By: grimar, rupprecht Differential Revision: https://reviews.llvm.org/D75592
2020-03-04 11:49:14 +08:00
# STATIC: DynamicSection [
# STATIC: FLAGS TEXTREL
# STATIC: TEXTREL 0x0
[ELF] - Implemented -znotext gold linker manual describes them as: -z text Do not permit relocations in read-only segments -z notext Permit relocations in read-only segments (default) In LLD default is to not permit them. Patch implements -z notext. Differential revision: https://reviews.llvm.org/D30530 llvm-svn: 297366
2017-03-09 16:48:34 +08:00
Don't create copy relocs or dummy plt's if given -z notext. Being passed -z notext is a pretty strong indication that the user is OK with text relocations. This is not the same behavior as bfd, but bfd defaults to -z notext, so it has to try to avoid text relocations and use them as a last resort. llvm-svn: 297789
2017-03-15 06:50:07 +08:00
# STATIC: Relocations [
Rename a test file and fix indentation. llvm-svn: 326504
2018-03-02 07:01:41 +08:00
# STATIC-NEXT: Section {{.*}} .rela.dyn {
[ELF][X86] Allow PT_LOAD to have overlapping p_offset ranges on EM_X86_64 Port the D64906 technique to EM_X86_64. Differential Revision: https://reviews.llvm.org/D67482 llvm-svn: 371958
2019-09-16 15:05:34 +08:00
# STATIC-NEXT: 0x201290 R_X86_64_64 bar 0x0
# STATIC-NEXT: 0x201298 R_X86_64_PC64 zed 0x0
Rename a test file and fix indentation. llvm-svn: 326504
2018-03-02 07:01:41 +08:00
# STATIC-NEXT: }
# STATIC-NEXT: ]
Set DF_TEXTREL to executables that need text relocations. Summary: If an executable needs text relocations, it should be marked as such so that the loader can prepare for text relocations. We currently create a dummy segment with DT_TEXTREL for that purpose. Generic ABI as of 2000 [1] mentioned that "Its [DT_TEXTREL's] use has been superseded by the DF_TEXTREL flag". However, it's actually not superseded even after 18 years. OpenBSD and musl recognize only DT_TEXTREL. So we still need to set both. [1] http://www.sco.com/developers/gabi/2000-07-17/ch5.dynamic.html Reviewers: rafael Subscribers: emaste, llvm-commits, arichardson Differential Revision: https://reviews.llvm.org/D43920 llvm-svn: 326503
2018-03-02 06:56:52 +08:00
[ELF] - Implemented -znotext gold linker manual describes them as: -z text Do not permit relocations in read-only segments -z notext Permit relocations in read-only segments (default) In LLD default is to not permit them. Patch implements -z notext. Differential revision: https://reviews.llvm.org/D30530 llvm-svn: 297366
2017-03-09 16:48:34 +08:00
foo:
.quad foo
Don't create copy relocs or dummy plt's if given -z notext. Being passed -z notext is a pretty strong indication that the user is OK with text relocations. This is not the same behavior as bfd, but bfd defaults to -z notext, so it has to try to avoid text relocations and use them as a last resort. llvm-svn: 297789
2017-03-15 06:50:07 +08:00
.quad bar
.quad zed - .