90a6bb30fa
It is possible that the remangled name for an intrinsic already exists with a different (and wrong) prototype within the module. As the bitcode reader keeps both versions of all remangled intrinsics around for a longer time, this can result in a crash, as can be seen in https://bugs.llvm.org/show_bug.cgi?id=50923 This patch makes 'remangleIntrinsicFunction' aware of this situation. When it is detected, it moves the version with the wrong prototype to a different name. That version will be removed anyway once the module is completely loaded. With thanks to @asbirlea for reporting this issue when trying out an lto build with the full restrict patches, and @efriedma for suggesting a sane resolution mechanism. Reviewed By: apilipenko Differential Revision: https://reviews.llvm.org/D105118
11 lines
310 B
LLVM
11 lines
310 B
LLVM
target datalayout = "e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128"
|
|
target triple = "x86_64-unknown-linux-gnu"
|
|
|
|
%aaa = type <{ %aab, i32, [4 x i8] }>
|
|
%aab = type { i64 }
|
|
%fum = type { %aac, i8, [7 x i8] }
|
|
%aac = type { [8 x i8] }
|
|
|
|
declare void @bar01(%aaa*)
|
|
declare void @bar02(%fum*)
|