Displaying 3 results from an estimated 3 matches for "07294d3c".
2012 Sep 26
0
[LLVMdev] [PATCH / PROPOSAL] bitcode encoding that is ~15% smaller for large bitcode files...
On 26 September 2012 01:08, Jan Voung <jvoung at chromium.org> wrote:
> - Forward references will create negative-valued ids (which end up being
> written out as large 32-bit integers, as far as I could tell).
Can you use an SLEB-like representation?
It's probably not going to be backwards compatible, but if there isn't
an SLEB/ULEB representation in bitcode, I'd say
2012 Sep 26
2
[LLVMdev] [PATCH / PROPOSAL] bitcode encoding that is ~15% smaller for large bitcode files...
...t the default N is 6 bits, but I haven't tried tweaking these
parameters.
> --
> cheers,
> --renato
>
> http://systemcall.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120926/07294d3c/attachment.html>
2012 Sep 26
9
[LLVMdev] [PATCH / PROPOSAL] bitcode encoding that is ~15% smaller for large bitcode files...
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