forked from OSchip/llvm-project
Change instrprof LLVM_VP_MAX_NUM_VALS_PER_SITE threshold.
We're having flaky failures on this test on the sanitizer slow buildbot. Not per-run flaky, but it'll be green for a while, then red for a while. I suspect that changes in codegen are causing the LLVM_VP_MAX_NUM_VALS_PER_SITE=150 to be above and below the limit sporadically. The limit on my machine using lld and a non-bootstrapped compiler is 175, but the bot uses GNU ld and ld.gold at different points, which could be affecting behaviour. Change this threshold to LLVM_VP_MAX_NUM_VALS_PER_SITE=130 in order to try and get it below the failure point, at least for the foreseeable future. http://lab.llvm.org:8011/#/builders/37/builds/2744
This commit is contained in:
parent
8998b811c9
commit
1be97975cc
|
@ -1,7 +1,7 @@
|
||||||
RUN: %clang_pgogen -O2 -mllvm -disable-vp=false -mllvm -vp-static-alloc=true -DSTRESS=1 -o %t.ir.warn %S/../Inputs/instrprof-value-prof-real.c
|
RUN: %clang_pgogen -O2 -mllvm -disable-vp=false -mllvm -vp-static-alloc=true -DSTRESS=1 -o %t.ir.warn %S/../Inputs/instrprof-value-prof-real.c
|
||||||
RUN: env LLVM_PROFILE_FILE=%t.ir.profraw LLVM_VP_MAX_NUM_VALS_PER_SITE=255 %run %t.ir.warn 2>&1 |FileCheck --check-prefix=WARNING %s
|
RUN: env LLVM_PROFILE_FILE=%t.ir.profraw LLVM_VP_MAX_NUM_VALS_PER_SITE=255 %run %t.ir.warn 2>&1 |FileCheck --check-prefix=WARNING %s
|
||||||
# Test that enough static counters have been allocated
|
# Test that enough static counters have been allocated
|
||||||
RUN: env LLVM_PROFILE_FILE=%t.ir.profraw LLVM_VP_MAX_NUM_VALS_PER_SITE=150 %run %t.ir.warn 2>&1 |FileCheck --check-prefix=NOWARNING --allow-empty %s
|
RUN: env LLVM_PROFILE_FILE=%t.ir.profraw LLVM_VP_MAX_NUM_VALS_PER_SITE=130 %run %t.ir.warn 2>&1 |FileCheck --check-prefix=NOWARNING --allow-empty %s
|
||||||
|
|
||||||
# WARNING: LLVM Profile Warning:
|
# WARNING: LLVM Profile Warning:
|
||||||
# NOWARNING-NOT: LLVM Profile Warning:
|
# NOWARNING-NOT: LLVM Profile Warning:
|
||||||
|
|
Loading…
Reference in New Issue