Beef up this test case a little by introducing a global variable name

conflict after upgrade resulting from collapsed type planes. The test now
checks to make sure llvm-upgrade produces appropriate warning messages.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@32913 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/test/Assembler/2002-12-15-GlobalResolve.ll b/test/Assembler/2002-12-15-GlobalResolve.ll
index 332b5324ee078a78460cb2842867d7e7b76186da..c17a20d7fd8fee92f6db0d7bbae3ebb4db64b832 100644 (file)
--- a/test/Assembler/2002-12-15-GlobalResolve.ll
+++ b/test/Assembler/2002-12-15-GlobalResolve.ll
@@ -1,9 +1,11 @@
-; RUN: llvm-upgrade < %s | llvm-as -o /dev/null -f
+; RUN: llvm-upgrade < %s 2>/dev/null | llvm-as -o /dev/null -f &&
+; RUN: llvm-upgrade < %s 2>&1 | grep "Cannot disambiguate global value '%X'" &&
+; RUN: llvm-upgrade < %s 2>&1 | grep "Renaming global value '%X' to '%X.un"
 
+%X = external global uint *
 %X = external global %T* 
 %X = external global int *
 
 %T = type int
 
 implementation
-