search for: coveragemappingformat

Hi all! It seems I came across on issue with coverage mapping (http://www.llvm.org/docs/CoverageMappingFormat.html) check on: llvm revision: r228136 clang Last Changed Rev: 228121 build: Debug+Asserts OS: ubuntu 14.04 Here is simple snippets test1.c: NOT OK ================== #include <stdio.h> static int foo() { return 42; } int main() { return 0; } ================== cp src/test1.c src/test....

...ion of the format of the profile data file. The Clang user guide here describes it as an ASCII text file: http://clang.llvm.org/docs/UsersManual.html#sample-profile-format Whereas the posts above and the referenced link describe it as a stream of bytes containing LEB128s: http://www.llvm.org/docs/CoverageMappingFormat.html >From experimenting with the latest trunk I can see the latter is correct (well, at least the file I get is not ASCII text). Should we update the Clang user guide documentation? Or am I just getting confused? Are there two formats, one used for coverage and one used for PGO? Cheers, D...

...data file. > > The Clang user guide here describes it as an ASCII text file: > http://clang.llvm.org/docs/UsersManual.html#sample-profile-format > > Whereas the posts above and the referenced link describe it as a stream of > bytes containing LEB128s: > http://www.llvm.org/docs/CoverageMappingFormat.html > > From experimenting with the latest trunk I can see the latter is correct > (well, at least the file I get is not ASCII text). > Should we update the Clang user guide documentation? > Or am I just getting confused? Are there two formats, one used for coverage > and one use...

...user guide here describes it as an ASCII text file: > > http://clang.llvm.org/docs/UsersManual.html#sample-profile-format > > > > Whereas the posts above and the referenced link describe it as a stream > of > > bytes containing LEB128s: > > http://www.llvm.org/docs/CoverageMappingFormat.html > > > > From experimenting with the latest trunk I can see the latter is correct > > (well, at least the file I get is not ASCII text). > > Should we update the Clang user guide documentation? > > Or am I just getting confused? Are there two formats, one used for...

Hi, I'd like to track not just at the function level, but also at the code block level. For example, for a if-else statement, I want to know when the if-branch or else-branch is enter/exit. Is there a clang option similar to -finstrument-functions for code blocks? Alternatively, I could manually insert the code to the IR .ll file. I see the generated .ll use the following function when

Can you tell us if you're continuing to use the same approach as described in one of the LLVM meetings, i.e. instrument at the clang AST level? Also, do you generate GCOV files, some yaml, or is this a separate format? And finally in the meeting you had given how you assign counters to the blocks, an algorithm to minimize the number of insertions. Is that algorithm a well-known one or a

...es it as an ASCII text file: > > http://clang.llvm.org/docs/UsersManual.html#sample-profile-format > > > > Whereas the posts above and the referenced link describe it as a stream > of > > bytes containing LEB128s: > > http://www.llvm.org/docs/CoverageMappingFormat.html > > > > From experimenting with the latest trunk I can see the latter is correct > > (well, at least the file I get is not ASCII text). > > Should we update the Clang user guide documentation? > > Or am I just getting confused? Are there two fo...

...r is this a separate format? > > It is a separate format. The code for reading/writing profile data is in compiler-rt/lib/profile/. > > There is also a separate format for mapping the profile data back to source locations for code coverage testing. Details here: http://www.llvm.org/docs/CoverageMappingFormat.html > >> >> And finally in the meeting you had given how you assign counters to >> the blocks, an algorithm to minimize the number of insertions. Is that >> algorithm a well-known one or a custom one? Is that described >> somewhere? > > It is a custom approac...