From: Reid Spencer Date: Tue, 17 Aug 2004 00:49:03 +0000 (+0000) Subject: Technical Corrections (thanks to Robert Mykland): X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=8996e55ff9f694f32215d4ded4679cbd6d26db8b;p=oota-llvm.git Technical Corrections (thanks to Robert Mykland): - Define the "opcode" data type and reference the Instruction.def file - Clean up the definition of symtab by indicating that it is composed of two llists. - Fix some broken links. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@15843 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/BytecodeFormat.html b/docs/BytecodeFormat.html index 76365b4ea0d..226cd9638be 100644 --- a/docs/BytecodeFormat.html +++ b/docs/BytecodeFormat.html @@ -254,6 +254,17 @@ variable bit rate encoding as described above.

A 64-bit signed integer that occupies from one to ten bytes using the signed variable bit rate encoding. + + opcode + An enumerated integer value used in the instruction + format that identifies the LLVM instruction opcode referenced. The + specific values used depend on the version of LLVM you're using. See the + + include/llvm/Instruction.def file for the definitive set of + opcode values used for your release. The opcode values are the first + argument to the various HANDLE_*_INST macros. + char A single unsigned character encoded into one byte @@ -644,7 +655,7 @@ sections.

block - Module Symbol Table + Module Symbol Table @@ -1159,7 +1170,7 @@ list for the function. block - The function's symbol + The function's symbol table containing only those symbols pertinent to the function (mostly block labels). @@ -1269,11 +1280,11 @@ of formats. See Instructions for details. 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.

+that follow describe the format of this first part 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 +shortened because they have large numbers of operands (e.g. PHI Node or +getelementptr). Each of the opcode, type, and operand fields is found in successive fields.

@@ -1329,7 +1340,7 @@ identifies this as an instruction of format 1. - + @@ -1460,18 +1471,15 @@ value are written. The format is given in the table below.

- - - - - - + + - - + +
2-7opcodeopcode Specifies the opcode of the instruction. Note that the maximum opcode value is 63.
Symbol Table Identifier (0x04)
uint32_vbrNumber of entries in type plane
symtab_entry*Provides the slot number of the type and its -name.llist(symtab_entry)A length list of symbol table entries for + Types +
symtab_plane*A type plane containing value slot number and -name for all values of the same type.llist(symtab_plane)A length list of planes of symbol table + entries for Values
@@ -1520,8 +1528,8 @@ format is given in the following table:

uint24_vbr - Slot number of the type or value being given -a name. + Slot number of the type or value being given a name. + uint32_vbr