[all-commits] [llvm/llvm-project] d5655c: [llvm-dwarfdump][Statistics] Don't count coverage ...

[chbessonova via All-commits]

  Branch: refs/heads/master
  Home:   https://github.com/llvm/llvm-project
  Commit: d5655c4d2e180b7eadb567ebf7e9a9393dec1355
      https://github.com/llvm/llvm-project/commit/d5655c4d2e180b7eadb567ebf7e9a9393dec1355
  Author: Kristina Bessonova <kbessonova at accesssoftek.com>
  Date:   2019-12-13 (Fri, 13 Dec 2019)

  Changed paths:
    M llvm/docs/CommandGuide/llvm-locstats.rst
    M llvm/test/tools/llvm-dwarfdump/X86/locstats.ll
    M llvm/test/tools/llvm-locstats/locstats.ll
    M llvm/tools/llvm-dwarfdump/Statistics.cpp
    M llvm/utils/llvm-locstats/llvm-locstats.py

  Log Message:
  -----------
  [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