File: 2003-11-18-TypeResolution.ll

package info (click to toggle)
llvm-toolchain-19 1%3A19.1.7-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,998,520 kB
  • sloc: cpp: 6,951,680; ansic: 1,486,157; asm: 913,598; python: 232,024; f90: 80,126; objc: 75,281; lisp: 37,276; pascal: 16,990; sh: 10,009; ml: 5,058; perl: 4,724; awk: 3,523; makefile: 3,167; javascript: 2,504; xml: 892; fortran: 664; cs: 573
file content (20 lines) | stat: -rw-r--r-- 664 bytes parent folder | download | duplicates (39) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
 
; Linking these two translation units causes there to be two LLVM values in the
; symbol table with the same name and same type.  When this occurs, the symbol
; table class is DROPPING one of the values, instead of renaming it like a nice
; little symbol table.  This is causing llvm-link to die, at no fault of its
; own.

; RUN: llvm-as < %s > %t.out2.bc
; RUN: echo "%%T1 = type opaque  @GVar = external global %%T1*" | llvm-as > %t.out1.bc
; RUN: llvm-link %t.out1.bc %t.out2.bc

%T1 = type opaque
%T2 = type i32
@GVar = global i32* null		; <i32**> [#uses=0]

define void @foo(i32* %X) {
	%X.upgrd.1 = bitcast i32* %X to %T1*		; <%T1*> [#uses=0]
	ret void
}