search for: pgoptim

...tried the following, as in the Clang user guide: $ clang++ -O2 -fprofile-instr-generate code.cc -o code $ LLVM_PROFILE_FILE="code-%p.profraw" ./code $ llvm-profdata merge -output=code.profdata code-*.profraw $ clang++ -O2 -fprofile-instr-use=code.profdata code.cc -o code This produces a PGOptimized executable which performs differently (in fact, better!) than a normal O2 build, so I think the "code.profdata" file produced by the commands above is valid. If I look inside "code.profdata" with a text editor, the file is most definitely not the ASCII-based sampling profil...

...ang user guide: > > $ clang++ -O2 -fprofile-instr-generate code.cc -o code > $ LLVM_PROFILE_FILE="code-%p.profraw" ./code > $ llvm-profdata merge -output=code.profdata code-*.profraw > $ clang++ -O2 -fprofile-instr-use=code.profdata code.cc -o code > > This produces a PGOptimized executable which performs differently (in fact, > better!) than a normal O2 build, so I think the "code.profdata" file produced > by the commands above is valid. > > If I look inside "code.profdata" with a text editor, the file is most > definitely not the ASC...

On Fri, May 22, 2015 at 11:16 AM, Dario Domizioli <dario.domizioli at gmail.com> wrote: > Hi all, > > I am a bit confused about the documentation 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

Hi all, I am a bit confused about the documentation 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