search for: classllvm_1_1instrprofreaderindex

...e 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_1InstrProfReaderIndex.html#acc49fd2c0a8c8dfc3e29b01e09869af7 ? That seems unnecessary. (it seems to be used for value profiling stuff for some reason?) -- Sean Silva > > David > > > > On Wed, Dec 9, 2015 at 7:52 AM, Diego Novillo via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >...

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