Displaying 4 results from an estimated 4 matches for "writestrtab".
2017 Apr 04
4
RFC: Adding a string table to the bitcode format
...le instead of before?
>
For implementation simplicity. The idea is that the BitcodeWriter would
have a member of type StringTableBuilder which would accumulate strings
while writing the bitcode module(s) (and symtab in the future). At the end,
the client would call something like BitcodeWriter::writeStrtab() which
would write out the string table.
>
> 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, which in
> multi-...
2017 Apr 04
2
RFC: Adding a string table to the bitcode format
...t;
>
> For implementation simplicity. The idea is that the BitcodeWriter would
> have a member of type StringTableBuilder which would accumulate strings
> while writing the bitcode module(s) (and symtab in the future). At the end,
> the client would call something like BitcodeWriter::writeStrtab() which
> would write out the string table.
>
>
> There is already a traversal of the module for value numbering, building
> the StringTable at the same time seems quite natural to me.
>
Other modules in the same bitcode file may need to add names to the string
table, and the sym...
2017 Apr 04
3
RFC: Adding a string table to the bitcode format
...t;
>
> For implementation simplicity. The idea is that the BitcodeWriter would
> have a member of type StringTableBuilder which would accumulate strings
> while writing the bitcode module(s) (and symtab in the future). At the end,
> the client would call something like BitcodeWriter::writeStrtab() which
> would write out the string table.
>
>
>>
>> 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 strin...
2017 Apr 04
5
RFC: Adding a string table to the bitcode format
Hi,
As part of PR27551 I want to add a string table to the bitcode format to
allow global value and comdat names to be shared with the proposed symbol
table (and, as side effects, allow comdat names to be shared with value
names, make bitcode files more compressible and make bitcode easier to
parse). The format of the string table would be a top-level block
containing a blob containing