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/relocation-non-alloc.s

61 lines
1.4 KiB
ArmAsm
Raw Normal View History

Add a test for relocations in non alloc sections. We already got this right, but we were not testing it. llvm-svn: 265471
2016-04-06 05:27:30 +08:00
// REQUIRES: x86
// RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %s -o %t
Add a few more cases to this test. It now documents how we currently handle relocations for alloc/non-alloc. llvm-svn: 266141
2016-04-13 06:08:23 +08:00
// RUN: ld.lld %t -o %t2 -shared
// RUN: llvm-readobj -s -section-data -r %t2 | FileCheck %s
Don't depend on lld creating relocations in ro segments. We currently don't do a good job of diagnosing inputs that would require dynamic relocations to be applied to read only segments. I am about to improve lld in that area, but unfortunately we developed tests that depend on the current behavior. To make clear what is actually changing, this first patch just updates tests to not depend on the current behavior. In most cases this just means using a rw section instead of a ro one, but that unfortunately changes many addresses. llvm-svn: 268145
2016-04-30 08:49:10 +08:00
// CHECK: Name: .data
Add a few more cases to this test. It now documents how we currently handle relocations for alloc/non-alloc. llvm-svn: 266141
2016-04-13 06:08:23 +08:00
// CHECK-NEXT: Type: SHT_PROGBITS
// CHECK-NEXT: Flags [
// CHECK-NEXT: SHF_ALLOC
Don't depend on lld creating relocations in ro segments. We currently don't do a good job of diagnosing inputs that would require dynamic relocations to be applied to read only segments. I am about to improve lld in that area, but unfortunately we developed tests that depend on the current behavior. To make clear what is actually changing, this first patch just updates tests to not depend on the current behavior. In most cases this just means using a rw section instead of a ro one, but that unfortunately changes many addresses. llvm-svn: 268145
2016-04-30 08:49:10 +08:00
// CHECK-NEXT: SHF_WRITE
Add a few more cases to this test. It now documents how we currently handle relocations for alloc/non-alloc. llvm-svn: 266141
2016-04-13 06:08:23 +08:00
// CHECK-NEXT: ]
ELF: Place relro sections after non-relro sections in r/w segment. This is in preparation for my next change, which will introduce a relro nobits section. That requires that relro sections appear at the end of the progbits part of the r/w segment so that the relro nobits section can appear contiguously. Because of the amount of churn required in the test suite, I'm making this change separately. llvm-svn: 291523
2017-01-10 09:21:30 +08:00
// CHECK-NEXT: Address: 0x1000
// CHECK-NEXT: Offset: 0x1000
Add a few more cases to this test. It now documents how we currently handle relocations for alloc/non-alloc. llvm-svn: 266141
2016-04-13 06:08:23 +08:00
// CHECK-NEXT: Size: 16
// CHECK-NEXT: Link: 0
// CHECK-NEXT: Info: 0
Don't depend on lld creating relocations in ro segments. We currently don't do a good job of diagnosing inputs that would require dynamic relocations to be applied to read only segments. I am about to improve lld in that area, but unfortunately we developed tests that depend on the current behavior. To make clear what is actually changing, this first patch just updates tests to not depend on the current behavior. In most cases this just means using a rw section instead of a ro one, but that unfortunately changes many addresses. llvm-svn: 268145
2016-04-30 08:49:10 +08:00
// CHECK-NEXT: AddressAlignment: 1
Add a few more cases to this test. It now documents how we currently handle relocations for alloc/non-alloc. llvm-svn: 266141
2016-04-13 06:08:23 +08:00
// CHECK-NEXT: EntrySize: 0
// CHECK-NEXT: SectionData (
When using Rela, don't write the addend to the output section. The Elf_Rela has an explicit addend. It doesn't need the addend to be written to the section being relocated. Since relative relocations are very common in the output, this is a noticeable speedup. The results I got were chromium master 4.778149487 patch 4.761120792 0.996436131802 chromium fast master 1.896253636 patch 1.840990582 0.970856718241 the gold plugin master 0.399337811 patch 0.392279276 0.982324401032 clang master 0.666873675 patch 0.665895708 0.998533504865 llvm-as master 0.037101095 patch 0.037123149 1.00059442989 the gold plugin fsds master 0.422473396 patch 0.414192879 0.980399909016 clang fsds master 0.747302008 patch 0.744843964 0.996710775599 llvm-as fsds master 0.033146245 patch 0.033064531 0.997534743377 scylla master 4.08857525 patch 4.082245184 0.998451767275 llvm-svn: 269417
2016-05-13 22:15:37 +08:00
// CHECK-NEXT: 0000: 00000000 00000000 00000000 00000000
Add a few more cases to this test. It now documents how we currently handle relocations for alloc/non-alloc. llvm-svn: 266141
2016-04-13 06:08:23 +08:00
// CHECK-NEXT: )
Add a test for relocations in non alloc sections. We already got this right, but we were not testing it. llvm-svn: 265471
2016-04-06 05:27:30 +08:00
// CHECK: Name: foo
// CHECK-NEXT: Type: SHT_PROGBITS
// CHECK-NEXT: Flags [
// CHECK-NEXT: ]
// CHECK-NEXT: Address: 0x0
// CHECK-NEXT: Offset:
Do not produce broken debug info. r267917 produces corrupted debug info because it didn't apply relocations to right offsets. llvm-svn: 267979
2016-04-29 11:21:08 +08:00
// CHECK-NEXT: Size: 32
Add a test for relocations in non alloc sections. We already got this right, but we were not testing it. llvm-svn: 265471
2016-04-06 05:27:30 +08:00
// CHECK-NEXT: Link: 0
// CHECK-NEXT: Info: 0
// CHECK-NEXT: AddressAlignment: 1
// CHECK-NEXT: EntrySize: 0
// CHECK-NEXT: SectionData (
ELF: Place relro sections after non-relro sections in r/w segment. This is in preparation for my next change, which will introduce a relro nobits section. That requires that relro sections appear at the end of the progbits part of the r/w segment so that the relro nobits section can appear contiguously. Because of the amount of churn required in the test suite, I'm making this change separately. llvm-svn: 291523
2017-01-10 09:21:30 +08:00
// CHECK-NEXT: 0000: 00100000 00000000 00100000 00000000
// CHECK-NEXT: 0010: 00100000 00000000 00100000 00000000
Add a test for relocations in non alloc sections. We already got this right, but we were not testing it. llvm-svn: 265471
2016-04-06 05:27:30 +08:00
// CHECK-NEXT: )
Add a few more cases to this test. It now documents how we currently handle relocations for alloc/non-alloc. llvm-svn: 266141
2016-04-13 06:08:23 +08:00
// CHECK: Relocations [
// CHECK-NEXT: Section ({{.}}) .rela.dyn {
ELF: Place relro sections after non-relro sections in r/w segment. This is in preparation for my next change, which will introduce a relro nobits section. That requires that relro sections appear at the end of the progbits part of the r/w segment so that the relro nobits section can appear contiguously. Because of the amount of churn required in the test suite, I'm making this change separately. llvm-svn: 291523
2017-01-10 09:21:30 +08:00
// CHECK-NEXT: 0x1000 R_X86_64_RELATIVE - 0x1000
// CHECK-NEXT: 0x1008 R_X86_64_64 zed 0x0
Add a few more cases to this test. It now documents how we currently handle relocations for alloc/non-alloc. llvm-svn: 266141
2016-04-13 06:08:23 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: ]
Don't depend on lld creating relocations in ro segments. We currently don't do a good job of diagnosing inputs that would require dynamic relocations to be applied to read only segments. I am about to improve lld in that area, but unfortunately we developed tests that depend on the current behavior. To make clear what is actually changing, this first patch just updates tests to not depend on the current behavior. In most cases this just means using a rw section instead of a ro one, but that unfortunately changes many addresses. llvm-svn: 268145
2016-04-30 08:49:10 +08:00
.data
Add a few more cases to this test. It now documents how we currently handle relocations for alloc/non-alloc. llvm-svn: 266141
2016-04-13 06:08:23 +08:00
.global zed
zed:
bar:
.quad bar
.quad zed
Add a test for relocations in non alloc sections. We already got this right, but we were not testing it. llvm-svn: 265471
2016-04-06 05:27:30 +08:00
.section foo
Add a few more cases to this test. It now documents how we currently handle relocations for alloc/non-alloc. llvm-svn: 266141
2016-04-13 06:08:23 +08:00
.quad bar
.quad zed
Do not produce broken debug info. r267917 produces corrupted debug info because it didn't apply relocations to right offsets. llvm-svn: 267979
2016-04-29 11:21:08 +08:00
.section foo
.quad bar
.quad zed