search for: instrprofrecord

...ta? > It's all profile data, actually. The heap utilization is massively dominated by the profile reader. > How large is the sample profile data fed to the compiler? > > For this run, the input file was 21Mb. > The indexed format profile size for clang is <100MB. The InstrProfRecord > for each function is read, used and discarded one at a time, so there > should not be problem as described. > Good. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20151210/635bfd6f/attachment.html...

I've been experimenting with profiled bootstraps using sample profiles. Initially, I made stage2 build stage3 while running under Perf. This produced a 20Gb profile which took too long to convert to LLVM, and used ~30Gb of RAM. So, I decided that this was not going to be very useful for general usage. I then changed the bootstrap to instead run each individual compile under Perf. This

...ec 9, 2015 at 12:14 PM, Xinliang David Li via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Can you extract the relevant part of the heap profile data? How large is > the sample profile data fed to the compiler? > > The indexed format profile size for clang is <100MB. The InstrProfRecord > for each function is read, used and discarded one at a time, so there > should not be problem as described. > If I'm reading the code right, we are also doing O(keys of the hash table) memory allocation in the indexed reader here: http://llvm.org/docs/doxygen/html/classllvm_1_1Inst...

...ual or non-llvm-style whitespace/wrapping/etc. Finally, the LLVM patch is quite large. We can probably make it a bit easier to stage and review by splitting out a couple of things and doing them first: 1. Changing the __llvm_profile_data variables so they're no longer const. 2. Adding the InstrProfRecord type and updating the unittests. Also, this type should just go in the InstrProf.h header, no need for its own. 3. Arguably, we could update the raw format and implement the RawInstrProfReader changes (but ignoring the new data) first. If you think this is worthwhile go ahead, but if i...

> Xinliang David Li <davidxl at google.com> writes: >>> From: <betulb at codeaurora.org> >>> Date: Tue, Apr 7, 2015 at 12:44 PM >>> Subject: [LLVMdev] IC profiling infrastructure >>> To: llvmdev at cs.uiuc.edu >>> >>> >>> >>> Hi All, >>> >>> We had sent out an RFC in October on indirect call