Displaying 2 results from an estimated 2 matches for "function_block_rel_id".
2012 Sep 26
0
[LLVMdev] [PATCH / PROPOSAL] bitcode encoding that is ~15% smaller for large bitcode files...
...code/LLVMBitCodes.h
> +++ b/include/llvm/Bitcode/LLVMBitCodes.h
> @@ -33,9 +33,9 @@ namespace bitc {
> UNUSED_ID1,
>
> CONSTANTS_BLOCK_ID,
> - FUNCTION_BLOCK_ID,
> + FUNCTION_BLOCK_ID, // Deprecated in favor of FUNCTION_BLOCK_ID_REL
FUNCTION_BLOCK_ID_REL -> FUNCTION_BLOCK_REL_ID
Is there any point in having this on a per-function basis, why not have it be
per-module?
>
> - UNUSED_ID2,
> + FUNCTION_BLOCK_REL_ID,
>
> VALUE_SYMTAB_BLOCK_ID,
> METADATA_BLOCK_ID,
> @@ -257,8 +257,9 @@ namespace bitc {
> SYNCHSCOPE_CROSSTHREAD = 1
&...
2012 Sep 26
9
[LLVMdev] [PATCH / PROPOSAL] bitcode encoding that is ~15% smaller for large bitcode files...
.... The common
case for this is PHI nodes, but in larger tests fewer bits *overall* are
used for INST_PHI.
- Doesn't help with constant operands. Their ids will now constantly
change...
- To retain backward compatibility with old bitcode files, I ended up using
up a new bitc value "bitc::FUNCTION_BLOCK_REL_ID" vs the existing
"bitc::FUNCTION_BLOCK_ID".
Are there known problems with this scheme?
Are there other ideas that have been floated around for reducing the size
of bitcode files?
In any case, the patch is attached if there is interest... If you want to
try out the patch, you can to...