File: secrel32-undef.s

package info (click to toggle)
llvm-toolchain-17 1%3A17.0.6-22
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 1,799,624 kB
  • sloc: cpp: 6,428,607; ansic: 1,383,196; asm: 793,408; python: 223,504; objc: 75,364; f90: 60,502; lisp: 33,869; pascal: 15,282; sh: 9,684; perl: 7,453; ml: 4,937; awk: 3,523; makefile: 2,889; javascript: 2,149; xml: 888; fortran: 619; cs: 573
file content (30 lines) | stat: -rw-r--r-- 948 bytes parent folder | download | duplicates (26) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
 
# RUN: llvm-mc -filetype=obj -triple i686-pc-win32 %s -o %t.obj
# RUN: llvm-readobj --symbols -r %t.obj | FileCheck %s

# Previously .secrel32 and .secidx relocations against undefined symbols
# resulted in an error. That was a mistake. The linker is fully capable of
# resolving these relocations against symbols in other object files. Such
# relocations can be found in the MSVCRT debug info describing linker-provided
# symbols like __safe_se_handler_table and __guard_fids_table.

.data
foo:
        .secrel32 bar
        .secidx baz


# CHECK: Relocations [
# CHECK:   Section (2) .data {
# CHECK:     0x0 IMAGE_REL_I386_SECREL bar
# CHECK:     0x4 IMAGE_REL_I386_SECTION baz
# CHECK:   }
# CHECK: ]

# CHECK:   Symbol {
# CHECK:     Name: bar
# CHECK-NEXT:     Value: 0
# CHECK-NEXT:     Section: IMAGE_SYM_UNDEFINED (0)
# CHECK:   Symbol {
# CHECK:     Name: baz
# CHECK-NEXT:     Value: 0
# CHECK-NEXT:     Section: IMAGE_SYM_UNDEFINED (0)