search for: mbref

...can write the following user code: // writes the output to dll_path with .dll replaced with .lib void ZigLLDDefToLib(Buf *def_contents, Buf *dll_path) { lld::coff::Config = new lld::coff::Configuration; auto mem_buf = MemoryBuffer::getMemBuffer(buf_ptr(def_contents)); MemoryBufferRef mbref(*mem_buf); lld::coff::parseModuleDefs(mbref); lld::coff::Config->OutputFile = buf_ptr(dll_path); lld::coff::writeImportLibrary(); } Then I give it def_contents that looks like: LIBRARY kernel32 EXPORTS ExitProcess GetConsoleMode GetStdHandle GetFileInformationByHandleEx WriteFile G...

...g a multi-module bitcode file would 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 functiona...

...; // writes the output to dll_path with .dll replaced with .lib >> void ZigLLDDefToLib(Buf *def_contents, Buf *dll_path) { >> lld::coff::Config = new lld::coff::Configuration; >> auto mem_buf = MemoryBuffer::getMemBuffer(buf_ptr(def_contents)); >> MemoryBufferRef mbref(*mem_buf); >> lld::coff::parseModuleDefs(mbref); >> lld::coff::Config->OutputFile = buf_ptr(dll_path); >> lld::coff::writeImportLibrary(); >> } >> >> >> Then I give it def_contents that looks like: >> LIBRARY kernel32 >> EXPORTS &...

...th with .dll replaced with .lib >>>> void ZigLLDDefToLib(Buf *def_contents, Buf *dll_path) { >>>> lld::coff::Config = new lld::coff::Configuration; >>>> auto mem_buf = MemoryBuffer::getMemBuffer(buf_ptr(def_contents)); >>>> MemoryBufferRef mbref(*mem_buf); >>>> lld::coff::parseModuleDefs(mbref); >>>> lld::coff::Config->OutputFile = buf_ptr(dll_path); >>>> lld::coff::writeImportLibrary(); >>>> } >>>> >>>> >>>> Then I give it def_contents that...

...module bitcode file would 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 That makes the API quite state...

...would 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 > > > > Th...

...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(); 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(...

...ch 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(); > > 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 &qu...

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

...r.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 mo...

...> 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 cont...