From: Reid Spencer
Date: Wed, 28 Feb 2007 02:33:06 +0000 (+0000)
Subject: Describe how arbitrary precision integers are written to the bytecode.
X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=7fc0832ee1a63a785335e710e6c7153f3cd082ad;p=oota-llvm.git
Describe how arbitrary precision integers are written to the bytecode.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34719 91177308-0d34-0410-b5e6-96231b3b80d8
---
diff --git a/docs/BytecodeFormat.html b/docs/BytecodeFormat.html
index b2370eecc4b..06320a30b4f 100644
--- a/docs/BytecodeFormat.html
+++ b/docs/BytecodeFormat.html
@@ -1275,10 +1275,18 @@ field definitions, based on type:
- 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.
+ - Signed Integers (sbyte,short,int,long) ≤ 64 bits. These are
+ written as an int64_vbr with the corresponding
+ value.
+ - Unsigned Integers (ubyte,ushort,uint,ulong) ≤ 64 bits. These
+ are written as an uint64_vbr with the corresponding
+ value.
+ - Integers > 64 bits. These are written as a length followed by a
+ series of 64-bit words. The length specifies the number of words that follow.
+ Any zero-valued high order words are elided. Words with the least significant
+ bits are written to the lowest file offsets (little endian). The length is
+ written as an uint32_vbr. Each word of the value
+ is written as an uint64_vbr.
- Floating Point. Both the float and double types are written
literally in binary format.
- Arrays. Arrays are written simply as a list of