search for: pr33500

Displaying 2 results from an estimated 2 matches for "pr33500".

Did you mean: pr33501
2017 Jun 19
3
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
...ng like that, then use llvm-cov on the original? > Coverage makes use of frontend-based instrumentation, which is much > less efficient than the IR-based kind. If we can find a way to map > counters inserted by IR PGO to AST nodes, we could improve the > situation. I filed: llvm.org/PR33500 <http://llvm.org/PR33500>. This would be nice... but I assume it's hard. :) > > 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 profil...
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