File: 2002-03-08-NameCollision2.ll

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 (13 lines) | stat: -rw-r--r-- 382 bytes parent folder | download | duplicates (22) 
1
2
3
4
5
6
7
8
9
10
11
12
13
 
; RUN: llvm-as %s -o /dev/null
; RUN: verify-uselistorder %s

; Another name collision problem.  Here the problem was that if a forward
; declaration for a method was found, that this would cause spurious conflicts
; to be detected between locals and globals.
;
@Var = external global i32		; <i32*> [#uses=0]

define void @foo() {
	%Var = alloca i32		; <i32*> [#uses=0]
	ret void
}