search for: mdvalueptr

...e module. > > > > The high level summary is that during the initial import it leaves the > > temporary metadata on the instructions that were imported, but saves > > the index used by the bitcode reader used to correlate with the > > metadata when it is ready (i.e. the MDValuePtrs index), and skips the > > metadata parsing. During finalization we parse just the metadata, and > > suture it up during metadata value mapping using the saved index. > > AFAICT, the gold-plugin currently does similar work. (Rafael knows > this code better (I've only intro...

...that would end up being all of the metadata in the module. The high level summary is that during the initial import it leaves the temporary metadata on the instructions that were imported, but saves the index used by the bitcode reader used to correlate with the metadata when it is ready (i.e. the MDValuePtrs index), and skips the metadata parsing. During finalization we parse just the metadata, and suture it up during metadata value mapping using the saved index. > >> >> >> b. Import Tuning: >> >> Tuning the import strategy will be an iterative process that will >&...

...functions imported by an earlier BitcodeReader instantiation. The high level summary is that during the initial import we leave the temporary metadata on the instructions that were imported, but save the index used by the bitcode reader used to correlate with the metadata when it is ready (i.e. the MDValuePtrs index), and skip the metadata parsing. During the ThinLTO pass finalization we parse just the metadata, and suture it up during metadata value mapping using the saved index. As mentioned earlier, this will be described in more detail when the patches are ready. 3. Stage 3: ThinLTO Tuning and Enh...

...y an earlier BitcodeReader instantiation. The > high level summary is that during the initial import we leave the > temporary metadata on the instructions that were imported, but save > the index used by the bitcode reader used to correlate with the > metadata when it is ready (i.e. the MDValuePtrs index), and skip the > metadata parsing. During the ThinLTO pass finalization we parse just > the metadata, and suture it up during metadata value mapping using the > saved index. As mentioned earlier, this will be described in more > detail when the patches are ready. > > >...

...codeReader instantiation. The >> high level summary is that during the initial import we leave the >> temporary metadata on the instructions that were imported, but save >> the index used by the bitcode reader used to correlate with the >> metadata when it is ready (i.e. the MDValuePtrs index), and skip the >> metadata parsing. During the ThinLTO pass finalization we parse just >> the metadata, and suture it up during metadata value mapping using the >> saved index. As mentioned earlier, this will be described in more >> detail when the patches are ready....

...t; high level summary is that during the initial import we leave the >>>>> temporary metadata on the instructions that were imported, but save >>>>> the index used by the bitcode reader used to correlate with the >>>>> metadata when it is ready (i.e. the MDValuePtrs index), and skip the >>>>> metadata parsing. During the ThinLTO pass finalization we parse just >>>>> the metadata, and suture it up during metadata value mapping using the >>>>> saved index. As mentioned earlier, this will be described in more >>...

...Reader instantiation. The > > high level summary is that during the initial import we leave the > > temporary metadata on the instructions that were imported, but save > > the index used by the bitcode reader used to correlate with the > > metadata when it is ready (i.e. the MDValuePtrs index), and skip the > > metadata parsing. During the ThinLTO pass finalization we parse just > > the metadata, and suture it up during metadata value mapping using the > > saved index. As mentioned earlier, this will be described in more > > detail when the patches are rea...

...tion. The > >> high level summary is that during the initial import we leave the > >> temporary metadata on the instructions that were imported, but save > >> the index used by the bitcode reader used to correlate with the > >> metadata when it is ready (i.e. the MDValuePtrs index), and skip the > >> metadata parsing. During the ThinLTO pass finalization we parse just > >> the metadata, and suture it up during metadata value mapping using the > >> saved index. As mentioned earlier, this will be described in more > >> detail when the...

...t;>>> high level summary is that during the initial import we leave the >>>> temporary metadata on the instructions that were imported, but save >>>> the index used by the bitcode reader used to correlate with the >>>> metadata when it is ready (i.e. the MDValuePtrs index), and skip the >>>> metadata parsing. During the ThinLTO pass finalization we parse just >>>> the metadata, and suture it up during metadata value mapping using the >>>> saved index. As mentioned earlier, this will be described in more >>>> det...

...tion. The >> > high level summary is that during the initial import we leave the >> > temporary metadata on the instructions that were imported, but save >> > the index used by the bitcode reader used to correlate with the >> > metadata when it is ready (i.e. the MDValuePtrs index), and skip the >> > metadata parsing. During the ThinLTO pass finalization we parse just >> > the metadata, and suture it up during metadata value mapping using the >> > saved index. As mentioned earlier, this will be described in more >> > detail when the...

...h level summary is that during the initial import we leave the > >> >> temporary metadata on the instructions that were imported, but save > >> >> the index used by the bitcode reader used to correlate with the > >> >> metadata when it is ready (i.e. the MDValuePtrs index), and skip the > >> >> metadata parsing. During the ThinLTO pass finalization we parse just > >> >> the metadata, and suture it up during metadata value mapping using > the > >> >> saved index. As mentioned earlier, this will be described in mo...

I've included below an RFC for implementing ThinLTO in LLVM, looking forward to feedback and questions. Thanks! Teresa RFC to discuss plans for implementing ThinLTO upstream. Background can be found in slides from EuroLLVM 2015: https://drive.google.com/open?id=0B036uwnWM6RWWER1ZEl5SUNENjQ&authuser=0) As described in the talk, we have a prototype implementation, and would like to