2015-08-11 02:28:24 +08:00
|
|
|
Test that we can handle shndx. The test file has a shndx despite having only
|
|
|
|
|
a few sections. One might consider it invalid, but it has a clear interpretation
|
|
|
|
|
and avoids needing 65K sections to test the corresponding code path.
|
|
|
|
|
|
2015-08-28 21:15:05 +08:00
|
|
|
RUN: lld -target x86_64-pc-linux -flavor gnu %p/Inputs/shndx.o-x86_64 -o %t.so -shared
|
2015-08-11 02:28:24 +08:00
|
|
|
RUN: llvm-readobj -s -t %t.so | FileCheck %s
|
|
|
|
|
|
|
|
|
|
CHECK: Name: .text
|
|
|
|
|
CHECK-NEXT: Type: SHT_PROGBITS (0x1)
|
|
|
|
|
CHECK-NEXT: Flags [ (0x6)
|
|
|
|
|
CHECK-NEXT: SHF_ALLOC (0x2)
|
|
|
|
|
CHECK-NEXT: SHF_EXECINSTR (0x4)
|
|
|
|
|
CHECK-NEXT: ]
|
|
|
|
|
CHECK-NEXT: Address: [[ADDR:.*]]
|
|
|
|
|
|
|
|
|
|
// CHECK: Symbol {
|
|
|
|
|
// CHECK: Name: foo
|
|
|
|
|
// CHECK-NEXT: Value: [[ADDR]]
|
