From eedde31b7ddf2faba84e5477d9830d24f58ec9ea Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Wed, 19 Nov 2003 01:03:16 +0000 Subject: [PATCH] New testcase for PR 130 llvm-svn: 10076 --- .../Linker/2003-11-18-TypeResolution.ll | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 llvm/test/Regression/Linker/2003-11-18-TypeResolution.ll diff --git a/llvm/test/Regression/Linker/2003-11-18-TypeResolution.ll b/llvm/test/Regression/Linker/2003-11-18-TypeResolution.ll new file mode 100644 index 000000000000..946c6a268fd1 --- /dev/null +++ b/llvm/test/Regression/Linker/2003-11-18-TypeResolution.ll @@ -0,0 +1,23 @@ +; 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.out[12].bc + + %T1 = type opaque + %T2 = type int + +%GVar = global %T2 * null + +implementation + +void %foo(%T2 * %X) { + %X = cast %T2* %X to %T1 * + ret void +} + +