This document describes the LLVM bytecode file format as of version 1.3. It specifies the binary encoding rules of the bytecode file format so that equivalent systems can encode bytecode files correctly. The LLVM bytecode representation is used to store the intermediate representation on disk in compacted form.

This section describes the general concepts of the bytecode file format without getting into bit and byte level specifics. Note that the LLVM bytecode format may change in the future, but will always be backwards compatible with older formats. This document only describes the most current version of the bytecode format.

LLVM bytecode files consist simply of a sequence of blocks of bytes. Each block begins with an header of two unsigned integers. The first value identifies the type of block and the second value provides the size of the block in bytes. The block identifier is used because it is possible for entire blocks to be omitted from the file if they are empty. The block identifier helps the reader determine which kind of block is next in the file. Note that blocks can be nested within other blocks.

All blocks are variable length, and the block header specifies the size of the block. All blocks begin on a byte index that is aligned to an even 32-bit boundary. That is, the first block is 32-bit aligned because it starts at offset 0. Each block is padded with zero fill bytes to ensure that the next block also starts on a 32-bit boundary.

LLVM Bytecode blocks often contain lists of things of a similar type. For example, a function contains a list of instructions and a function type contains a list of argument types. There are two basic types of lists: length lists, and null terminated lists, as described here:

• Length Lists. Length lists are simply preceded by the number of items in the list. The bytecode reader will read the count first and then iterate that many times to read in the list contents.
• Null Terminated Lists. For some lists, the number of elements in the list is not readily available at the time of writing the bytecode. In these cases, the list is terminated by some null value. What constitutes a null value differs, but it almost always boils down to a zero value.

Fields are units of information that LLVM knows how to write atomically. Most fields have a uniform length or some kind of length indication built into their encoding. For example, a constant string (array of bytes) is written simply as the length followed by the characters. Although this is similar to a list, constant strings are treated atomically and are thus fields.

Fields use a condensed bit format specific to the type of information they must contain. As few bits as possible are written for each field. The sections that follow will provide the details on how these fields are written and how the bits are to be interpreted.

To support cross-platform differences, the bytecode file is aligned on certain boundaries. This means that a small amount of padding (at most 3 bytes) will be added to ensure that the next entry is aligned to a 32-bit boundary.

Each field that can be put out is encoded into the file using a small set of primitives. The rules for these primitives are described below.

Variable Bit Rate Encoding

Most of the values written to LLVM bytecode files are small integers. To minimize the number of bytes written for these quantities, an encoding scheme similar to UTF-8 is used to write integer data. The scheme is known as variable bit rate (vbr) encoding. In this encoding, the high bit of each byte is used to indicate if more bytes follow. If (byte & 0x80) is non-zero in any given byte, it means there is another byte immediately following that also contributes to the value. For the final byte (byte & 0x80) is false (the high bit is not set). In each byte only the low seven bits contribute to the value. Consequently 32-bit quantities can take from one to five bytes to encode. In general, smaller quantities will encode in fewer bytes, as follows:

Note that in practice, the tenth byte could only encode bit 63 since the maximum quantity to use this encoding is a 64-bit integer.

Signed VBR values are encoded with the standard vbr encoding, but with the sign bit as the low order bit instead of the high order bit. This allows small negative quantities to be encoded efficiently. For example, -3 is encoded as "((3 << 1) | 1)" and 3 is encoded as "(3 << 1) | 0)", emitted with the standard vbr encoding above.

The table below defines the encoding rules for type names used in the descriptions of blocks and fields in the next section. Any type name with the suffix _vbr indicate a quantity that is encoded using variable bit rate encoding as described above.

The bytecode format uses the notion of a "slot" to reference Types and Values. Since the bytecode file is a direct representation of LLVM's intermediate representation, there is a need to represent pointers in the file. Slots are used for this purpose. For example, if one has the following assembly:

there are two definitions. The definition of %MyVar uses %MyType. In the C++ IR this linkage between %MyVar and %MyType is explicit through the use of C++ pointers. In bytecode, however, there's no ability to store memory addresses. Instead, we compute and write out slot numbers for every Type and Value written to the file.

A slot number is simply an unsigned 32-bit integer encoded in the variable bit rate scheme (see encoding). This ensures that low slot numbers are encoded in one byte. Through various bits of magic LLVM attempts to always keep the slot numbers low. The first attempt is to associate slot numbers with their "type plane". That is, Values of the same type are written to the bytecode file in a list (sequentially). Their order in that list determines their slot number. This means that slot #1 doesn't mean anything unless you also specify for which type you want slot #1. Types are handled specially and are always written to the file first (in the Global Type Pool) and in such a way that both forward and backward references of the types can often be resolved with a single pass through the type pool.

Slot numbers are also kept small by rearranging their order. Because of the structure of LLVM, certain values are much more likely to be used frequently in the body of a function. For this reason, a compaction table is provided in the body of a function if its use would make the function body smaller. Suppose you have a function body that uses just the types "int*" and "{double}" but uses them thousands of time. Its worthwhile to ensure that the slot number for these types are low so they can be encoded in a single byte (via vbr). This is exactly what the compaction table does.

This section provides the general structur of the LLVM bytecode file format. The bytecode file format requires blocks to be in a certain order and nested in a particular way so that an LLVM module can be constructed efficiently from the contents of the file. This ordering defines a general structure for bytecode files as shown below. The table below shows the order in which all block types may appear. Please note that some of the blocks are optional and some may be repeated. The structure is fairly loose because optional blocks, if empty, are completely omitted from the file.

Use the links in the table or see Block Types for details about the contents of each of the block types.

This section provides the detailed layout of the individual block types in the LLVM bytecode file format.

The signature occurs in every LLVM bytecode file and is always first. It simply provides a few bytes of data to identify the file as being an LLVM bytecode file. This block is always four bytes in length and differs from the other blocks because there is no identifier and no block length at the start of the block. Essentially, this block is just the "magic number" for the file.

The module block contains a small pre-amble and all the other blocks in the file. The table below shows the structure of the module block. Note that it only provides the module identifier, size of the module block, and the format information. Everything else is contained in other blocks, described in other sections.

The format information field is encoded into a 32-bit vbr-encoded unsigned integer as shown in the following table.

Of particular note, the bytecode format number is simply a 28-bit monotonically increase integer that identifies the version of the bytecode format (which is not directly related to the LLVM release number). The bytecode versions defined so far are (note that this document only describes the latest version, 1.3):

• #0: LLVM 1.0 & 1.1
• #1: LLVM 1.2
• #2: LLVM 1.3

Note that we plan to eventually expand the target description capabilities of bytecode files to target triples.

The global type pool consists of type definitions. Their order of appearance in the file determines their slot number (0 based). Slot numbers are used to replace pointers in the intermediate representation. Each slot number uniquely identifies one entry in a type plane (a collection of values of the same type). Since all values have types and are associated with the order in which the type pool is written, the global type pool must be written as the first block of a module. If it is not, attempts to read the file will fail because both forward and backward type resolution will not be possible.

The type pool is simply a list of type definitions, as shown in the table below.

1. Repeated field.

Types in the type pool are defined using a different format for each basic type of type as given in the following sections.

Primitive Types

The primitive types encompass the basic integer and floating point types

1. See the definition of Type::TypeID in Type.h for the numeric equivalents of the primitive type ids.

Function Types

1. Repeated field.
2. Optional field.

Structure Types

1. Repeatable field.

Array Types

Pointer Types

Opaque Types

The module global info block contains the definitions of all global variables including their initializers and the declaration of all functions. The format is shown in the table below:

1. Both these fields are repeatable but in pairs.
2. Optional field.
3. Repeatable field.

Global variables are written using a single uint32_vbr that encodes information about the global variable. The table below provides the bit layout of the value written for each global variable.

1. This bit determines whether the constant initializer field follows immediately after this field

A constant pool defines as set of constant values. There are actually two types of constant pool blocks: one for modules and one for functions. For modules, the block begins with the constant strings encountered anywhere in the module. For functions, the block begins with types only encountered in the function. In both cases the header is identical. The tables the follow, show the header, module constant pool preamble, function constant pool preamble, and the part common to both function and module constant pools.

Common Block Header

Module Constant Pool Preamble (constant strings)

1. Repeated field.

Function Constant Pool Preamble (function types)

The structure of the types for functions is identical to the Global Type Pool. Please refer to that section for the details.

Common Part (other constants)

Constants come in many shapes and flavors. The sections that followe define the format for each of them. All constants start with a uint32_vbr encoded integer that provides the number of operands for the constant. For primitive, structure, and array constants, this will always be zero since those types of constants have no operands. In this case, we have the following field definitions:

• Bool. This is written as an uint32_vbr of value 1U or 0U.
• Signed Integers (sbyte,short,int,long). These are written as an int64_vbr with the corresponding value.
• Unsigned Integers (ubyte,ushort,uint,ulong). These are written as an uint64_vbr with the corresponding value.
• Floating Point. Both the float and double types are written literally in binary format.
• Arrays. Arrays are written simply as a list of uint32_vbr encoded slot numbers to the constant element values.
• Structures. Structures are written simply as a list of uint32_vbr encoded slot numbers to the constant field values of the structure.

When the number of operands to the constant is non-zero, we have a constant expression and its field format is provided in the table below.

1. Both these fields are repeatable but only in pairs.

To be determined.

1. Note that if the linkage type is "External" then none of the other fields will be present as the function is defined elsewhere.
2. Note that only one of the constant pool or compaction table will be written. Compaction tables are only written if they will actually save bytecode space. If not, then a regular constant pool is written.

Compaction tables are part of a function definition. They are merely a device for reducing the size of bytecode files. The size of a bytecode file is dependent on the value of the slot numbers used because larger values use more bytes in the variable bit rate encoding scheme. Furthermore, the compresses instruction format reserves only six bits for the type of the instruction. In large modules, declaring hundreds or thousands of types, the values of the slot numbers can be quite large. However, functions may use only a small fraction of the global types. In such cases a compaction table is created that maps the global type and value slot numbers to smaller values used by a function. Compaction tables have the format shown in the table below.

1. Repeated field.
2. This field's encoding varies depending on the size of the type plane. See Type and Length for further details.

The type and length of a compaction table type plane is encoded differently depending on the length of the plane. For planes of length 1 or 2, the length is encoded into bits 0 and 1 of a uint32_vbr and the type is encoded into bits 2-31. Because type numbers are often small, this often saves an extra byte per plane. If the length of the plane is greater than 2 then the encoding uses a uint32_vbr for each of the length and type, in that order.

The instructions in a function are written as a simple list. Basic blocks are inferred by the terminating instruction types. The format of the block is given in the following table.

1. A repeated field with a variety of formats. See Instructions for details.

For brevity, instructions are written in one of four formats, depending on the number of operands to the instruction. Each instruction begins with a uint32_vbr that encodes the type of the instruction as well as other things. The tables that follow describe the format of this first word of each instruction.

Instruction Format 0

This format is used for a few instructions that can't easily be optimized because they have large numbers of operands (e.g. PHI Node or getelementptr). Each of the opcode, type, and operand fields is as successive fields.

1. Repeatable field (limit given by previous field).
2. Note that if the instruction is a getelementptr and the type of the operand is a sequential type (array or pointer) then the slot number is shifted up two bits and the low order bits will encode the type of index used, as follows: 0=uint, 1=int, 2=ulong, 3=long.

Instruction Format 1

This format encodes the opcode, type and a single operand into a single uint32_vbr as follows:

Instruction Format 2

This format encodes the opcode, type and two operands into a single uint32_vbr as follows:

Instruction Format 3

This format encodes the opcode, type and three operands into a single uint32_vbr as follows:

A symbol table can be put out in conjunction with a module or a function. A symbol table is a list of type planes. Each type plane starts with the number of entries in the plane and the type plane's slot number (so the type can be looked up in the global type pool). For each entry in a type plane, the slot number of the value and the name associated with that value are written. The format is given in the table below.

1. Repeated field.

A symbol table plane provides the symbol table entries for all values of a common type. The encoding is given in the following table:

A symbol table entry provides the assocation between a type or value's slot number and the name given to that type or value. The format is given in the following table:

This section describes the differences in the Bytecode Format across LLVM versions. The versions are listed in reverse order because it assumes the current version is as documented in the previous sections. Each section here describes the differences between that version and the one that follows.

In version 1.2, the Type class in the LLVM IR derives from the Value class. This is not the case in version 1.3. Consequently, in version 1.2 the notion of a "Type Type" was used to write out values that were Types. The types always occuped plane 12 (corresponding to the TypeTyID) of any type planed set of values. In 1.3 this representation is not convenient because the TypeTyID (12) is not present and its value is now used for LabelTyID. Consequently, the data structures written that involve types do so by writing all the types first and then each of the value planes according to those types. In version 1.2, the types would have been written intermingled with the values.

In version 1.2, the getelementptr instruction required a ubyte type index for accessing a structure field and a long type index for accessing an array element. Consequently, it was only possible to access structures of 255 or fewer elements. Starting in version 1.3, this restriction was lifted. Structures must now be indexed with uint constants. Arrays may now be indexed with int, uint, long, or ulong typed values. The consequence of this was that the bytecode format had to change in order to accommodate the larger range of structure indices.

In version 1.1, the zero value for primitives was explicitly encoded into the bytecode format. Since these zero values are constant values in the LLVM IR and never change, there is no reason to explicitly encode them. This explicit encoding was removed in version 1.2.

In version 1.1, the Module Global Info block was not aligned causing the next block to be read in on an unaligned boundary. This problem was corrected in version 1.2.

None. Version 1.0 and 1.1 bytecode formats are identical.