Displaying 6 results from an estimated 6 matches for "dllvm_build_instrumented_coverage".
Did you mean:
llvm_build_instrumented_coverage
2017 Jun 27
2
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
On 6/27/2017 1:47 PM, Xinliang David Li wrote:
>
>
> On Mon, Jun 26, 2017 at 7:24 PM, Friedman, Eli
> <efriedma at codeaurora.org <mailto:efriedma at codeaurora.org>> wrote:
>
> On 6/19/2017 7:29 PM, Vedant Kumar wrote:
>>
>>>> We can reduce testing time by *not* instrumented basic tools
>>>> like count, not, FileCheck etc. I
2017 Jun 27
3
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
On 6/19/2017 7:29 PM, Vedant Kumar wrote:
>
>>> We can reduce testing time by *not* instrumented basic tools like
>>> count, not, FileCheck etc. I filed: llvm.org/PR33501
>>> <http://llvm.org/PR33501>.
>>>
>>>> 3. The generated profile information takes up a lot of space: llc
>>>> generates a 90MB profraw file.
>>>
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
2017 Jun 27
2
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
I had an old build of llc with FE instrumentation, the name section size is
about 5MB. Using coverage is likely to cause the name section to be larger
as there are more references to dead/unused function names.
What do you see when
readelf --string-dump=__llvm_prf_names llc
David
On Tue, Jun 27, 2017 at 2:23 PM, Xinliang David Li <davidxl at google.com>
wrote:
>
>
> On Tue,
2017 Jun 19
3
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
On 6/18/2017 3:51 PM, Vedant Kumar wrote:
>> 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 __llvm_prf_names section. This took me half a day to figure out.
2017 Jun 27
4
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
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