599f95ecc2
When making changes that have a large impact on coverage counter creation, this makes it easier to see whether the number of physical counters has changed. (The highest counter ID seen in coverage maps is not necessarily the same as the number of physical counters actually used by the instrumented code, but it's the best approximation we can get from looking only at the coverage maps, and it should be reasonably accurate in most cases.) |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
This tool extracts coverage mapping information from an LLVM IR assembly file
(.ll), and prints it in a more human-readable form that can be used for
snapshot tests.
The output format is mostly arbitrary, so it's OK to change the output as long as any affected tests are also re-blessed. However, the output should be consistent across different executions on different platforms, so avoid printing any information that is platform-specific or non-deterministic.
Demangle mode
When run as coverage-dump --demangle, this tool instead functions as a
command-line demangler that can be invoked by llvm-cov.