search for: blockinfo_block

Hello, llvm-bcanalyzer told me that the size of the BLOCKINFO_BLOCK of my file is "1.345017e+01" percent of the whole file. This is not very readable. The attached patch prints the percentage without scientific notation so we get something bit more readable: Block ID #0 (BLOCKINFO_BLOCK): Num Instances: 1 Total Size: 637b/79.62B/19W %...

I wrote in a few weeks ago about writing an independent implementation of Bitcode and updating the docs to be more complete. Attached is a patch to docs/BitCodeFormat.html that adds a lot of information that was previously only available by reading the source code. It also corrects some errors. Josh -------------- next part -------------- An HTML attachment was scrubbed... URL:

...ader will hold a pointer to the ThinLTO data structure to be populated with the ThinLTO information (data structures described in a separate “ThinLTO File API and Data Structures” RFC which should be sent out at the same time). It will ignore all MODULE_BLOCK subblocks except the THINLTO_BLOCK, the BLOCKINFO_BLOCK containing abbrev IDs, and the VALUE_SYMTAB_BLOCK. The VALUE_SYMTAB_BLOCK parser is specialized/simplified since there will not be any Value objects created during ThinLTO parsing, we simply need to correlate each string with its ValueID in the VALUE_SYMTAB_BLOCK record. Bitcode Combined Function...

...nter to the ThinLTO data structure to be > populated with the ThinLTO information (data structures described in a > separate “ThinLTO File API and Data Structures” RFC which should be sent > out at the same time). It will ignore all MODULE_BLOCK subblocks except the > THINLTO_BLOCK, the BLOCKINFO_BLOCK containing abbrev IDs, and the > VALUE_SYMTAB_BLOCK. The VALUE_SYMTAB_BLOCK parser is specialized/simplified > since there will not be any Value objects created during ThinLTO parsing, > we simply need to correlate each string with its ValueID in the > VALUE_SYMTAB_BLOCK record. > &g...