search for: d24786

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 API would look like for reading and writing multiple modules. Here's what I have in mind. To create a multi-module bitcode fil...

...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 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 API would look like for reading and writing multiple modules. > > Here's what I...

...llingbourne <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 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 API would look like for reading and writing multiple modules. > > Here's what I have in mind. To create a...

...>> 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 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 >&g...

...>>>>> 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 API w...

...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 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 API would look like for reading and writing multiple modules. >> >> Here's what I have i...

...> >> 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 API would look like for reading and writing multiple modules. > >> &gt...

...t; >> >> >> 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 API would look like for...