File: secrel32-undef.s

package info (click to toggle)
llvm-toolchain-11 1%3A11.0.1-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 995,808 kB
  • sloc: cpp: 4,767,656; ansic: 760,916; asm: 477,436; python: 170,940; objc: 69,804; lisp: 29,914; sh: 23,855; f90: 18,173; pascal: 7,551; perl: 7,471; ml: 5,603; awk: 3,489; makefile: 2,573; xml: 915; cs: 573; fortran: 503; javascript: 452
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)