From f9a3ec86c138177c7d9b3a9d119e6d2247d14bd8 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Sun, 26 Apr 2009 22:21:57 +0000 Subject: 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 --- docs/BitCodeFormat.html | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'docs') 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:
 [SETBID (#1), blockid]
 [DEFINE_ABBREV, ...]
+[BLOCKNAME, ...name...]
+[SETRECORDNAME, RecordID, ...name...]
 
@@ -582,6 +584,15 @@ in BLOCKINFO blocks receive abbreviation IDs as described in DEFINE_ABBREV.

+

The BLOCKNAME 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.

+ +

The SETRECORDNAME 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.

+

Note that although the data in BLOCKINFO blocks is described as "metadata," the abbreviations they contain are essential for parsing records -- cgit v1.1