summaryrefslogtreecommitdiffstats
path: root/llvm/utils/llvm-locstats/llvm-locstats.py
diff options
context:
space:
mode:
authorKristina Bessonova <kbessonova@accesssoftek.com>2019-12-05 16:45:57 +0300
committerKristina Bessonova <kbessonova@accesssoftek.com>2019-12-13 17:34:58 +0300
commitd5655c4d2e180b7eadb567ebf7e9a9393dec1355 (patch)
treecdb86002e7dc20b7dd8eae1a370b4ba8661d7fb7 /llvm/utils/llvm-locstats/llvm-locstats.py
parent97572775d2fe088d8059b3a9423f6d8539fafe33 (diff)
downloadbcm5719-llvm-d5655c4d2e180b7eadb567ebf7e9a9393dec1355.tar.gz
bcm5719-llvm-d5655c4d2e180b7eadb567ebf7e9a9393dec1355.zip
[llvm-dwarfdump][Statistics] Don't count coverage less than 1% as 0%
Summary: This is a follow up for D70548. Currently, variables with debug info coverage between 0% and 1% are put into zero-bucket. D70548 changed the way statistics calculate a variable's coverage: we began to use enclosing scope rather than a possible variable life range. Thus more variables might be moved to zero-bucket despite they have some debug info coverage. The patch is to distinguish between a variable that has location info but it's significantly less than its enclosing scope and a variable that doesn't have it at all. Reviewers: djtodoro, aprantl, dblaikie, avl Subscribers: llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D71070
Diffstat (limited to 'llvm/utils/llvm-locstats/llvm-locstats.py')
-rwxr-xr-xllvm/utils/llvm-locstats/llvm-locstats.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/utils/llvm-locstats/llvm-locstats.py b/llvm/utils/llvm-locstats/llvm-locstats.py
index 2bbc3f1986d..0d177ef294e 100755
--- a/llvm/utils/llvm-locstats/llvm-locstats.py
+++ b/llvm/utils/llvm-locstats/llvm-locstats.py
@@ -15,7 +15,7 @@ from subprocess import Popen, PIPE
def coverage_buckets():
yield '0%'
- yield '[1%,10%)'
+ yield '(0%,10%)'
for start in range(10, 91, 10):
yield '[{0}%,{1}%)'.format(start, start + 10)
yield '100%'
OpenPOWER on IntegriCloud