Displaying 2 results from an estimated 2 matches for "r270020".
2017 Jun 19
3
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
...ge I
>> got was "Assertion `!Key.empty()' failed." from llvm-cov.
>
> I expect llvm-cov to print out "Failed to load coverage: <reason>" in
> this situation. There was some work done to tighten up error reporting
> in ProfileData and its clients in r270020. If your host toolchain does
> have these changes, please file a bug, and I'll have it fixed.
Host toolchain is trunk clang... but using system binutils (which is
2.24 on my Ubuntu 14.04 system... and apparently that's too old per
David Li's response). Anyway, filed
https://bug...
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