search for: coveragemappinggen

...s only the 3 lines that are executable while SBCC counts all 10 because at least one counter will span the whole block. llvm-cov has no visibility into the source code so we can’t reliably clean this up from there. Instead I’m thinking of modifying the coverage mapping generator (clang/lib/CodeGen/CoverageMappingGen.cpp) to (optionally) record the line numbers for source lines that have real code on them and emit this informaiton alongside the coverage-mapping data in the object files. In llvm-cov I can then use the extra info so SBCC counts blank lines the same way gcov does. I’m writing to solicit feedbac...

+ Vedant Hi Hal, thanks. I apologize if my answers aren't as thorough as you would like; what I'm proposing is simply an extension to the existing infrastructure, so it would be enabled automatically as part of code coverage. Mapping of branch regions would be done in CoverageMappingGen and instrumented using the same profiling instrumentation mechanism under CodeGenPGO::mapRegionCounters() and around CodeGenFunction::EmitBranchOnBoolExpr() . In fact, as I mention below, we'd largely be reusing the same profiling counters (except in at least one exception case that I describe...

With llc, the size of the names section can vary widely depending on the value of -DLLVM_TARGETS_TO_BUILD. Enabling coverage shouldn't increase the name section size much. I only see one place where this happens, and it's relatively cold: http://lab.llvm.org:8080/coverage/coverage-reports/llvm/coverage/Users/buildslave/jenkins/sharedspace/clang-stage2-coverage-R at

Vedant Kumar asked me to post my design thoughts concerning branch coverage at llvm-dev since there is general interest. My team at Texas Instruments is developing an embedded ARM C/C++ compiler with LLVM. I would like to enhance LLVM's code coverage capability with branch condition coverage (for C/C++), similar to GCC/GCOV support for branch coverage. This is useful for TI, and I think

...> while SBCC counts all 10 because at least one counter will span the whole > block. llvm-cov has no visibility into the source code so we can’t reliably > clean this up from there. > > > > Instead I’m thinking of modifying the coverage mapping generator > (clang/lib/CodeGen/CoverageMappingGen.cpp) to (optionally) record the > line numbers for source lines that have real code on them and emit this > informaiton alongside the coverage-mapping data in the object files. In > llvm-cov I can then use the extra info so SBCC counts blank lines the same > way gcov does. I’m writin...