search for: d84473

...EB128 encoding of the compressed size in bytes - the message compressed by zlib::compressed in that order. llvm-readobj ------------ We read the .llvm_dump section. We dump each chunk of compressed data one after another. Existing Implementation ======================= https://reviews.llvm.org/D84473 Future Directions ================= The proposal above does not support the ThinLTO build flow. To support that, I am thinking about putting the message as metadata in the IR at the prelink stage. Thoughts? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http...

...;> in that order. >> >> llvm-readobj >> ------------ >> >> We read the .llvm_dump section.  We dump each chunk of compressed data >> one after another. >> >> Existing Implementation >> ======================= >> https://reviews.llvm.org/D84473 >> >> Future Directions >> ================= >> >> The proposal above does not support the ThinLTO build flow.  To >> support that, I am thinking about putting the message as metadata in >> the IR at the prelink stage. >> >> Thoughts? >> &...

...> > > > llvm-readobj > > ------------ > > > > We read the .llvm_dump section. We dump each chunk of compressed data > > one after another. > > > > Existing Implementation > > ======================= > > > > https://reviews.llvm.org/D84473 > > > > Future Directions > > ================= > > > > The proposal above does not support the ThinLTO build flow. To > > support that, I am thinking about putting the message as metadata in > > the IR at the prelink stage. > > > > Thoughts? &...