File: secrel32-undef.s

package info (click to toggle)
swiftlang 6.0.3-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 2,519,992 kB
  • sloc: cpp: 9,107,863; ansic: 2,040,022; asm: 1,135,751; python: 296,500; objc: 82,456; f90: 60,502; lisp: 34,951; pascal: 19,946; sh: 18,133; perl: 7,482; ml: 4,937; javascript: 4,117; makefile: 3,840; awk: 3,535; xml: 914; fortran: 619; cs: 573; ruby: 573
file content (30 lines) | stat: -rw-r--r-- 948 bytes parent folder | download | duplicates (25) 
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)