diff options
author | Chris Lattner <sabre@nondot.org> | 2009-04-26 22:21:57 +0000 |
---|---|---|
committer | Chris Lattner <sabre@nondot.org> | 2009-04-26 22:21:57 +0000 |
commit | f9a3ec86c138177c7d9b3a9d119e6d2247d14bd8 (patch) | |
tree | 15986c2b097351545c57cf4bd2e8c3b4e3d97cd7 /docs/BitCodeFormat.html | |
parent | 7919b966a8fd8f98346216e79df6f4722693be22 (diff) | |
download | external_llvm-f9a3ec86c138177c7d9b3a9d119e6d2247d14bd8.zip external_llvm-f9a3ec86c138177c7d9b3a9d119e6d2247d14bd8.tar.gz external_llvm-f9a3ec86c138177c7d9b3a9d119e6d2247d14bd8.tar.bz2 |
Add two new record types to the blockinfo block:
BLOCKNAME and SETRECORDNAME. This allows a bitcode
file to be self describing with pretty names for
records and blocks in addition to numbers. This
enhances llvm-bcanalyzer to use this to print prettily.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@70165 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/BitCodeFormat.html')
-rw-r--r-- | docs/BitCodeFormat.html | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/docs/BitCodeFormat.html b/docs/BitCodeFormat.html index 54b9361..8813b01 100644 --- a/docs/BitCodeFormat.html +++ b/docs/BitCodeFormat.html @@ -563,6 +563,8 @@ blocks. The currently specified records are: <pre> [SETBID (#1), blockid] [DEFINE_ABBREV, ...] +[BLOCKNAME, ...name...] +[SETRECORDNAME, RecordID, ...name...] </pre> </div> @@ -582,6 +584,15 @@ in <tt>BLOCKINFO</tt> blocks receive abbreviation IDs as described in <tt><a href="#DEFINE_ABBREV">DEFINE_ABBREV</a></tt>. </p> +<p>The <tt>BLOCKNAME</tt> can optionally occur in this block. The elements of +the record are the bytes for the string name of the block. llvm-bcanalyzer uses +this to dump out bitcode files symbolically.</p> + +<p>The <tt>SETRECORDNAME</tt> record can optionally occur in this block. The +first entry is a record ID number and the rest of the elements of the record are +the bytes for the string name of the record. llvm-bcanalyzer uses +this to dump out bitcode files symbolically.</p> + <p> Note that although the data in <tt>BLOCKINFO</tt> blocks is described as "metadata," the abbreviations they contain are essential for parsing records |