llvm-project/llvm/test/Instrumentation/InstrProfiling
Ellis Hoag 11d3074267 [InstrProf] Add single byte coverage mode
Use the llvm flag `-pgo-function-entry-coverage` to create single byte "counters" to track functions coverage. This mode has significantly less size overhead in both code and data because
  * We mark a function as "covered" with a store instead of an increment which generally requires fewer assembly instructions
  * We use a single byte per function rather than 8 bytes per block

The trade off of course is that this mode only tells you if a function has been covered. This is useful, for example, to detect dead code.

When combined with debug info correlation [0] we are able to create an instrumented Clang binary that is only 150M (the vanilla Clang binary is 143M). That is an overhead of 7M (4.9%) compared to the default instrumentation (without value profiling) which has an overhead of 31M (21.7%).

[0] https://groups.google.com/g/llvm-dev/c/r03Z6JoN7d4

Reviewed By: kyulee

Differential Revision: https://reviews.llvm.org/D116180
2022-01-27 17:38:55 -08:00
..
X86
always_inline.ll
atomic-updates.ll [InstrProf] Use i32 for GEP index from lowering llvm.instrprof.increment 2021-11-19 15:45:14 -08:00
comdat.ll
coverage.ll [InstrProf] Add single byte coverage mode 2022-01-27 17:38:55 -08:00
debug-info-correlate-coverage.ll [InstrProf] Add single byte coverage mode 2022-01-27 17:38:55 -08:00
debug-info-correlate.ll [Try2][InstrProf] Attach debug info to counters 2021-12-16 14:20:30 -08:00
early-exit.ll
icall-comdat.ll
icall-nocomdat.ll
no-counters.ll
noruntime.ll
platform.ll
profiling.ll
runtime-counter-relocation.ll [InstrProf] Use i32 for GEP index from lowering llvm.instrprof.increment 2021-11-19 15:45:14 -08:00