d3d49bca3e
Fixes a bug introduced by
commit f95b2f1acf11 ("Reland [InstrProf][compiler-rt] Enable MC/DC
Support in LLVM Source-based Code Coverage (1/3)")
createDataVariable() needs to check that a data variable wasn't already
created before creating it. Previously, this was done inadvertantly in
getOrCreateRegionCounters(), which checked that the RegionCounters was
not created multiple times before creating the counter section and the
data variable. When the creation of the data variable was abstracted
into its own function (createDataVariable()), there was no corresponding
check. This was failing on a case in which an instrumented function was
being inlined into multiple functions and a duplicate data variable was
created, which led to a segfault in emitNameData(). Test case added
based on the repro that also ensures a single data variable was created
in this case.
27 lines
673 B
LLVM
27 lines
673 B
LLVM
;; Check that only one data variable is created when an instrprof.increment is
|
|
;; inlined into more than one function.
|
|
; RUN: opt %s -passes='cgscc(inline),instrprof' -S | FileCheck %s
|
|
|
|
target triple = "x86_64-unknown-linux-gnu"
|
|
|
|
; CHECK: @__profd_foobar = private global
|
|
; CHECK-NOT @__profd_foobar
|
|
|
|
declare void @llvm.instrprof.increment(ptr %0, i64 %1, i32 %2, i32 %3)
|
|
@__profn_foobar = private constant [6 x i8] c"foobar"
|
|
|
|
define internal void @foobar() {
|
|
call void @llvm.instrprof.increment(ptr @__profn_foobar, i64 123456, i32 32, i32 0)
|
|
ret void
|
|
}
|
|
|
|
define void @foo() {
|
|
call void @foobar()
|
|
ret void
|
|
}
|
|
|
|
define void @bar() {
|
|
call void @foobar()
|
|
ret void
|
|
}
|