search for: entersubblock

...yway: > diff --git a/include/llvm/Bitcode/BitstreamReader.h b/include/llvm/Bitcode/BitstreamReader.h > index 3daef78..840f57e 100644 > --- a/include/llvm/Bitcode/BitstreamReader.h > +++ b/include/llvm/Bitcode/BitstreamReader.h > @@ -409,7 +409,7 @@ public: > } > > /// EnterSubBlock - Having read the ENTER_SUBBLOCK abbrevid, enter > - /// the block, and return true if the block is valid. > + /// the block, and return true if the block has an error. > bool EnterSubBlock(unsigned BlockID, unsigned *NumWordsP = 0) { > // Save the current block's state on...

Hi all, I've been looking into how to make llvm bitcode files smaller. There is one simple change that appears to shrink linked bitcode files by about 15%. See this spreadsheet for some rough data: https://docs.google.com/spreadsheet/ccc?key=0AjRrJHQc4_bddEtJdjdIek5fMDdIdFFIZldZXzdWa0E The change is in how operand ids are encoded in bitcode files. Rather than use an "absolute

...I simply continue to assume that we will have two METADATA_BLOCKs at module level and that the kinds will always be in the latter? 3) Another option is to peek inside the METADATA_BLOCK to check the first record's type, and if it isn't METADATA_KIND, skip the rest of the block. Looks like EnterSubBlock already optionally returns the size of the block in words, so I could use that to compute the bitcode offset to jump to before reading the first record, in case it is the wrong METADATA_BLOCK and I want to skip it. Thoughts? Thanks, Teresa -- Teresa Johnson | Software Engineer | tejohnson at go...

On Tue, Apr 4, 2017 at 12:36 PM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > On 2017-Apr-04, at 12:12, Peter Collingbourne <peter at pcc.me.uk> wrote: > > On Mon, Apr 3, 2017 at 8:13 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> >> On Apr 3, 2017, at 7:08 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: >>