search for: hasglobalvaluesummary

...iter.h > >> would have a member function 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? 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 summar...

...member function 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? > > > 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 "readGlobalValueSum...

...eader class. Each of the functional reader APIs in ReaderWriter.h > would have a member function 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(); > 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 > > > > That makes the API quite stateful, you may have good imple...

...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? >> >> >> 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. >> >>> W...

...functional reader APIs in ReaderWriter.h >> would have a member function 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.parseBitcod...

...be supported with a BitcodeReader class. Each of the functional reader APIs in ReaderWriter.h would have a member function 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(); 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 We'd continue to support the existing functional APIs in ReaderWriter.h for convenience in the com...

...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? >>> >>> >>> This would be the equivalent to the existing llvm::hasGlobalValueSummary() >>> function, which currently controls whether we compile a module with regular >>> LTO or with ThinL...

...ith a BitcodeReader class. Each of the functional reader APIs in ReaderWriter.h would have a member function 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(); > 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 That makes the API quite stateful, you may have good implementation reason for this, b...