search for: bitsrequiredfortypeindices

...the > API could be: > > BitcodeWriter W(OS); > W.writeModule(M1); > // delete M1 > // ... > // create M2 > W.writeModule(M2); > > (Maybe you had this in mind, but the API naming didn’t reflect it so I’m > not sure). > In the API I prototyped, I took the maximum BitsRequiredForTypeIndices value from all the modules, and used it to produce the abbreviations for the top level block info block (without this I was seeing "Unexpected abbrev ordering!" errors in the bitcode writer as a result of emitting the "same" abbreviation multiple times). That would have required...

...Writer W(OS); >> W.writeModule(M1); >> // delete M1 >> // ... >> // create M2 >> W.writeModule(M2); >> >> (Maybe you had this in mind, but the API naming didn’t reflect it so I’m >> not sure). > > > In the API I prototyped, I took the maximum BitsRequiredForTypeIndices value > from all the modules, and used it to produce the abbreviations for the top/ > level block info block (without this I was seeing "Unexpected abbrev > ordering!" errors in the bitcode writer as a result of emitting the "same" > abbreviation multiple times). Tha...

...;> // delete M1 > >> // ... > >> // create M2 > >> W.writeModule(M2); > >> > >> (Maybe you had this in mind, but the API naming didn’t reflect it so I’m > >> not sure). > > > > > > In the API I prototyped, I took the maximum BitsRequiredForTypeIndices > value > > from all the modules, and used it to produce the abbreviations for the > top/ > > level block info block (without this I was seeing "Unexpected abbrev > > ordering!" errors in the bitcode writer as a result of emitting the > "same" > &gt...

> 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 modules. In https://reviews.llvm.org/D24786 <https://reviews.llvm.org/D24786> I took a step

...gt;> // create M2 >> >> W.writeModule(M2); >> >> >> >> (Maybe you had this in mind, but the API naming didn’t reflect it so >> >> I’m >> >> not sure). >> > >> > >> > In the API I prototyped, I took the maximum BitsRequiredForTypeIndices >> > value >> > from all the modules, and used it to produce the abbreviations for the >> > top/ >> > level block info block (without this I was seeing "Unexpected abbrev >> > ordering!" errors in the bitcode writer as a result of emitting the...

...t;>>> W.writeModule(M2); >>>>> >>>>> (Maybe you had this in mind, but the API naming didn’t reflect it so >>>>> I’m >>>>> not sure). >>>> >>>> >>>> In the API I prototyped, I took the maximum BitsRequiredForTypeIndices >>>> value >>>> from all the modules, and used it to produce the abbreviations for the >>>> top/ >>>> level block info block (without this I was seeing "Unexpected abbrev >>>> ordering!" errors in the bitcode writer as a result o...

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 modules. In https://reviews.llvm.org/D24786 I took a step towards that by proposing a change to the module format so that the block info block is stored at the top level. The next step is to think about what the

...(M2); >>>>>> >>>>>> (Maybe you had this in mind, but the API naming didn’t reflect it so >>>>>> I’m >>>>>> not sure). >>>>> >>>>> >>>>> In the API I prototyped, I took the maximum BitsRequiredForTypeIndices >>>>> value >>>>> from all the modules, and used it to produce the abbreviations for the >>>>> top/ >>>>> level block info block (without this I was seeing "Unexpected abbrev >>>>> ordering!" errors in the bitcode...