summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api
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 /lldb/packages/Python/lldbsuite/test/python_api
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 'lldb/packages/Python/lldbsuite/test/python_api')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud