search for: readglobalvaluesummary

Displaying 6 results from an estimated 6 matches for "readglobalvaluesummary".

2016 Oct 28
0
RFC: APIs for bitcode files containing multiple modules
...tion on BitcodeReader. We would also have a next() >> member function which would move to the next module in the file. For >> example: >> >> BitcodeReader R(MBRef); >> Expected<bool> B = R.hasGlobalValueSummary(); What's this used for? Would there be a "readGlobalValueSummary()" similar to function summaries? >> std::unique_ptr<Module> M1 = R.getLazyModule(Ctx); // lazily load the >> first module >> R.next(); >> std::unique_ptr<Module> M2 = R.parseBitcodeFile(Ctx); // eagerly load the >> second module I'm very excited...
2016 Oct 28
2
RFC: APIs for bitcode files containing multiple modules
...> >> Expected<bool> B = R.hasGlobalValueSummary(); > > What's this used for? This would be the equivalent to the existing llvm::hasGlobalValueSummary() function, which currently controls whether we compile a module with regular LTO or with ThinLTO. Would there be a "readGlobalValueSummary()" > similar to function summaries? > There would be a getModuleSummaryIndex() which again would be similar to llvm::getModuleSummaryIndex(). Note that the module summary already covers all global values, not just functions. >> std::unique_ptr<Module> M1 = R.getLazyModule(C...
2016 Oct 26
2
RFC: APIs for bitcode files containing multiple modules
On Tue, Oct 25, 2016 at 8:36 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > On Oct 25, 2016, at 6:28 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > > Hi all, > > As mentioned in my recent RFC entitled "RFC: a more detailed design for > ThinLTO + vcall CFI" I would like to introduce the ability for bitcode > files to contain multiple
2016 Oct 28
0
RFC: APIs for bitcode files containing multiple modules
...GlobalValueSummary(); >> >> What's this used for? > > > This would be the equivalent to the existing llvm::hasGlobalValueSummary() > function, which currently controls whether we compile a module with regular > LTO or with ThinLTO. > >> Would there be a "readGlobalValueSummary()" >> similar to function summaries? > > > There would be a getModuleSummaryIndex() which again would be similar to > llvm::getModuleSummaryIndex(). Note that the module summary already covers > all global values, not just functions. > >> >> std::unique_ptr&...
2016 Oct 28
2
RFC: APIs for bitcode files containing multiple modules
...>> What's this used for? >> >> >> This would be the equivalent to the existing llvm::hasGlobalValueSummary() >> function, which currently controls whether we compile a module with regular >> LTO or with ThinLTO. >> >>> Would there be a "readGlobalValueSummary()" >>> similar to function summaries? >> >> >> There would be a getModuleSummaryIndex() which again would be similar to >> llvm::getModuleSummaryIndex(). Note that the module summary already covers >> all global values, not just functions. >> &gt...
2016 Oct 28
0
RFC: APIs for bitcode files containing multiple modules
...d for? >>> >>> >>> This would be the equivalent to the existing llvm::hasGlobalValueSummary() >>> function, which currently controls whether we compile a module with regular >>> LTO or with ThinLTO. >>> >>>> Would there be a "readGlobalValueSummary()" >>>> similar to function summaries? >>> >>> >>> There would be a getModuleSummaryIndex() which again would be similar to >>> llvm::getModuleSummaryIndex(). Note that the module summary already covers >>> all global values, not just...