Displaying 3 results from an estimated 3 matches for "bitcodeencod".
Did you mean:
bitcodeend
2012 Nov 09
1
[LLVMdev] [PATCH] -emit-bitcode-version
...tion. What about the original use-abs-operands? Do you think that what more reasonably scope this?
And so properly scoping my proposal I see that I don't want IR compatibility as much as I want encoding options. So with that in mind maybe I need to go back to the drawing board and propose a BitcodeEncoder?BitcodeCompressor?
> 2. The use case for it is also very narrow (in contrast to having the *reader* handle old files, which many scenarios benefit from).
Yep can't argue that. And I really like that reader is backwards compatible.
> 3. The open source project as a whole benefits fro...
2012 Nov 09
0
[LLVMdev] [PATCH] -emit-bitcode-version
On Nov 8, 2012, at 7:09 AM, Joe Abbey <jabbey at arxan.com> wrote:
>>> The problem we face is that bitcode changes, and when it does… future versions
>>> can read it, but past versions are left in the lurch. For instance LLVM 3.2svn
>>> can BitcodeReader from LLVM 3.1, but LLVM 3.1 can't BitcodeReader LLVM 3.2
>>> (after r165739.) There was an
2012 Nov 08
2
[LLVMdev] [PATCH] -emit-bitcode-version
On Nov 8, 2012, at 3:31 AM, Duncan Sands <baldrick at free.fr> wrote:
> Hi Joe,
>
>> We have a tool which reads in bitcode, processes it, and re-emits it. We use
>> this tool as a flexible way to integrate our tool into the Xcode, Android NDK,
>> Chromium, and Linux build process.
>>
>> The problem we face is that bitcode changes, and when it does…