Displaying 5 results from an estimated 5 matches for "strtab_block".
2017 Apr 04
4
RFC: Adding a string table to the bitcode format
...<MODULE_BLOCK>
> <VERSION op0=2>
> <COMDAT op0=0 ...> ; name = foo
> <FUNCTION op0=0 ...> ; name = foo
> <GLOBALVAR op0=4 ...> ; name = bar
> <ALIAS op0=8 ...> ; name = baz
> ; function bodies, etc.
> </MODULE_BLOCK>
> <STRTAB_BLOCK>
> <STRTAB_BLOB blob="foo\0bar\0baz\0">
> </STRTAB_BLOCK>
>
>
> Why is the string table after the module instead of before?
>
>
> Each STRTAB_BLOCK would apply to all preceding MODULE_BLOCKs. This means
> that bitcode files can continue to be co...
2017 Apr 04
5
RFC: Adding a string table to the bitcode format
...would look like as bcanalyzer output:
<MODULE_BLOCK>
<VERSION op0=2>
<COMDAT op0=0 ...> ; name = foo
<FUNCTION op0=0 ...> ; name = foo
<GLOBALVAR op0=4 ...> ; name = bar
<ALIAS op0=8 ...> ; name = baz
; function bodies, etc.
</MODULE_BLOCK>
<STRTAB_BLOCK>
<STRTAB_BLOB blob="foo\0bar\0baz\0">
</STRTAB_BLOCK>
Each STRTAB_BLOCK would apply to all preceding MODULE_BLOCKs. This means
that bitcode files can continue to be concatenated with "llvm-cat -b".
(Normally bitcode files would contain a single string table, wh...
2017 Apr 04
4
RFC: Adding a string table to the bitcode format
...<MODULE_BLOCK>
> <VERSION op0=2>
> <COMDAT op0=0 ...> ; name = foo
> <FUNCTION op0=0 ...> ; name = foo
> <GLOBALVAR op0=4 ...> ; name = bar
> <ALIAS op0=8 ...> ; name = baz
> ; function bodies, etc.
> </MODULE_BLOCK>
> <STRTAB_BLOCK>
> <STRTAB_BLOB blob="foo\0bar\0baz\0">
> </STRTAB_BLOCK>
>
>
> Why is the string table after the module instead of before?
>
For implementation simplicity. The idea is that the BitcodeWriter would
have a member of type StringTableBuilder which would ac...
2017 Apr 04
2
RFC: Adding a string table to the bitcode format
...<VERSION op0=2>
>> <COMDAT op0=0 ...> ; name = foo
>> <FUNCTION op0=0 ...> ; name = foo
>> <GLOBALVAR op0=4 ...> ; name = bar
>> <ALIAS op0=8 ...> ; name = baz
>> ; function bodies, etc.
>> </MODULE_BLOCK>
>> <STRTAB_BLOCK>
>> <STRTAB_BLOB blob="foo\0bar\0baz\0">
>> </STRTAB_BLOCK>
>>
>>
>> Why is the string table after the module instead of before?
>>
>
> For implementation simplicity. The idea is that the BitcodeWriter would
> have a member of...
2017 Apr 04
3
RFC: Adding a string table to the bitcode format
...<VERSION op0=2>
>> <COMDAT op0=0 ...> ; name = foo
>> <FUNCTION op0=0 ...> ; name = foo
>> <GLOBALVAR op0=4 ...> ; name = bar
>> <ALIAS op0=8 ...> ; name = baz
>> ; function bodies, etc.
>> </MODULE_BLOCK>
>> <STRTAB_BLOCK>
>> <STRTAB_BLOB blob="foo\0bar\0baz\0">
>> </STRTAB_BLOCK>
>>
>>
>> Why is the string table after the module instead of before?
>>
>
> For implementation simplicity. The idea is that the BitcodeWriter would
> have a member of...