fhahn added a comment.
To reproduce the issue you could use
+; Check that we only add a single summary entry for multiple definitions
+; of a linkonce_odr function
+
+; RUN: opt -module-summary %s -o %t1.bc
+; RUN: opt -module-summary %s -o %t2.bc
+; RUN: llvm-lto -thinlto-action=thinlink -o %t3.bc %t1.bc %t2.bc
+; RUN: llvm-bcanalyzer -dump %t3.bc | FileCheck %s
+
+define linkonce_odr void @foo(i8*) {
+ ret void
+}
+; CHECK: <GLOBALVAL_SUMMARY_BLOCK
+; CHECK: <VALUE_GUID
+; CHECK-NEXT: <COMBINED
+; CHECK-NOT: <COMBINED
+; CHECK: </GLOBALVAL_SUMMARY_BLOCK>
I've been debugging this issue using an index + bitcode files provided by a
third party, I'll try to get information on how they generated the index.
https://reviews.llvm.org/D35081
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
