1*9880d681SAndroid Build Coastguard Worker; RUN: llvm-as %s -o /dev/null 2*9880d681SAndroid Build Coastguard Worker; RUN: verify-uselistorder %s 3*9880d681SAndroid Build Coastguard Worker 4*9880d681SAndroid Build Coastguard Worker; Another name collision problem. Here the problem was that if a forward 5*9880d681SAndroid Build Coastguard Worker; declaration for a method was found, that this would cause spurious conflicts 6*9880d681SAndroid Build Coastguard Worker; to be detected between locals and globals. 7*9880d681SAndroid Build Coastguard Worker; 8*9880d681SAndroid Build Coastguard Worker@Var = external global i32 ; <i32*> [#uses=0] 9*9880d681SAndroid Build Coastguard Worker 10*9880d681SAndroid Build Coastguard Workerdefine void @foo() { 11*9880d681SAndroid Build Coastguard Worker %Var = alloca i32 ; <i32*> [#uses=0] 12*9880d681SAndroid Build Coastguard Worker ret void 13*9880d681SAndroid Build Coastguard Worker} 14