File: alias.ll

package info (click to toggle)
llvm-toolchain-9 1%3A9.0.1-16
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 882,436 kB
  • sloc: cpp: 4,167,636; ansic: 714,256; asm: 457,610; python: 155,927; objc: 65,094; sh: 42,856; lisp: 26,908; perl: 7,786; pascal: 7,722; makefile: 6,881; ml: 5,581; awk: 3,648; cs: 2,027; xml: 888; javascript: 381; ruby: 156
file content (37 lines) | stat: -rw-r--r-- 1,421 bytes parent folder | download | duplicates (20)
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
31
32
33
34
35
36
37
; RUN: llvm-link %s %S/Inputs/alias.ll -S -o - | FileCheck --check-prefix=C1 %s
; RUN: llvm-link %S/Inputs/alias.ll %s -S -o - | FileCheck --check-prefix=C2 %s

; FIXME:
; The C1 direction is incorrect.
; When moving an alias to an existing module and we want to discard the aliasee
; (the C2 case), the IRMover knows to copy the aliasee as internal.
; When moving a replacement to an aliasee to a module that has an alias (C1),
; a replace all uses with blindly changes the alias.
; The C1 case doesn't happen when using a system linker with a plugin because
; the linker does full symbol resolution first.
; Given that this is a problem only with llvm-link and its 1 module at a time
; linking, it should probably learn to changes the aliases in the destination
; before using the IRMover.

@foo = weak global i32 0
; C1-DAG: @foo = alias i32, i32* @zed
; C2-DAG: @foo = alias i32, i32* @zed

@bar = alias i32, i32* @foo
; C1-DAG: @bar = alias i32, i32* @foo

; C2-DAG: @foo.1 = internal global i32 0
; C2-DAG: @bar = alias i32, i32* @foo.1

@foo2 = weak global i32 0
; C1-DAG: @foo2 = alias i16, bitcast (i32* @zed to i16*)
; C2-DAG: @foo2 = alias i16, bitcast (i32* @zed to i16*)

@bar2 = alias i32, i32* @foo2
; C1-DAG: @bar2 = alias i32, bitcast (i16* @foo2 to i32*)

; C2-DAG: @foo2.2 = internal global i32 0
; C2-DAG: @bar2 = alias i32, i32* @foo2.2

; C1-DAG: @zed = global i32 42
; C2-DAG: @zed = global i32 42