From bcc47419d9a88e6b58a9e2a7c0ee4c7bf43e91b4 Mon Sep 17 00:00:00 2001 From: Mehdi Amini Date: Sat, 28 May 2016 17:26:03 +0000 Subject: ValueMapper: fix assertion when null-mapping a constant for linking metadata Summary: When RF_NullMapMissingGlobalValues is set, mapValue can return null for GlobalValue. When mapping the operands of a constant that is referenced from metadata, we need to handle this case and actually return null instead of mapping this constant. Reviewers: dexonsmith, rafael Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D20713 llvm-svn: 271129 --- llvm/test/Linker/null_mapping_constant.ll | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 llvm/test/Linker/null_mapping_constant.ll (limited to 'llvm/test') diff --git a/llvm/test/Linker/null_mapping_constant.ll b/llvm/test/Linker/null_mapping_constant.ll new file mode 100644 index 00000000000..a7e7770dd27 --- /dev/null +++ b/llvm/test/Linker/null_mapping_constant.ll @@ -0,0 +1,11 @@ +; RUN: llvm-link %s -S -o - | FileCheck %s +; Check that the constant is not linked and the metadata is correctly referencing a nullptr +; CHECK: !0 = !{!"foo", null, i64 16} + + + +target datalayout = "e-m:o-i64:64-f80:128-n8:16:32:64-S128" +target triple = "x86_64-apple-macosx10.12.0" +@foo = external unnamed_addr constant { [4 x i8*], [32 x i8] }, align 32 +!llvm.bitsets = !{!0} +!0 = !{!"foo", [4 x i8*]* getelementptr inbounds ({ [4 x i8*], [32 x i8] }, { [4 x i8*], [32 x i8] }* @foo, i32 0, i32 0), i64 16} -- cgit v1.2.3