Displaying 2 results from an estimated 2 matches for "pr33499".
Did you mean:
33499
2017 Jun 19
3
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
...t; to 250 seconds.
>
> The binary size increase comes from coverage mapping data, counter
> increment instrumentation, and profiling metadata.
>
> The coverage mapping section is highly compressible, but exploiting
> the compressibility has proven to be tricky. I filed: llvm.org/PR33499
> <http://llvm.org/PR33499>.
If I'm cross-compiling for a target where the space matters, can I rid
of the data for the copy on the device using "strip -R __llvm_covmap" or
something like that, then use llvm-cov on the original?
> Coverage makes use of frontend-based...
2017 Jun 17
3
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
I've started looking at the state of code coverage recently; we figured
LLVM itself would be a good test to figure out how mature it is, so I
gave it a shot. My experience:
1. You have to specify -DLLVM_USE_LINKER=gold (or maybe lld works; I
didn't try). If you link with binutils ld, the program will generate
broken profile information. Apparently, the linked binary is missing
the