[PATCH] D12618: Reserve a vendor reserved block ID for bitcode

Mehdi Amini via llvm-commits llvm-commits at lists.llvm.org
Wed Sep 16 10:39:56 PDT 2015


> On Sep 10, 2015, at 7:47 PM, Alex Rosenberg <alexr at leftfield.org> wrote:
> 
> alexr added a subscriber: alexr.
> alexr added a comment.
> 
> So, we went through this last year.... http://lists.llvm.org/pipermail/llvm-dev/2014-November/078498.html
> 
> If we add a vendor block, we should at a minimum define a way to identify which vendor it is, in case we are handed bitcode from somewhere else.
> Bike shed away, but there should be something simple enough at the start that can tell us we're looking at the wrong thing.


The way I do it internally right now is by using a “magic” at the beginning of the block. We could ask “by convention” implementer to always write a (32bits?) unique id at the beginning of the block, but it would be up to the vendor to follow this convention. Does this match what you have in mind?

— 
Mehdi


More information about the llvm-commits mailing list