summaryrefslogtreecommitdiffstats
path: root/llvm/docs/BytecodeFormat.html
diff options
context:
space:
mode:
authorReid Spencer <rspencer@reidspencer.com>2007-02-28 02:33:06 +0000
committerReid Spencer <rspencer@reidspencer.com>2007-02-28 02:33:06 +0000
commitccaec8e7c4257fb19efb973f64d828f9c8fc6f62 (patch)
tree3baa0087012fc2b2c4712786e9f86b6f09481ae2 /llvm/docs/BytecodeFormat.html
parentb5cf20c9397b177605e692f204f6562f210c6733 (diff)
downloadbcm5719-llvm-ccaec8e7c4257fb19efb973f64d828f9c8fc6f62.tar.gz
bcm5719-llvm-ccaec8e7c4257fb19efb973f64d828f9c8fc6f62.zip
Describe how arbitrary precision integers are written to the bytecode.
llvm-svn: 34719
Diffstat (limited to 'llvm/docs/BytecodeFormat.html')
-rw-r--r--llvm/docs/BytecodeFormat.html16
1 files changed, 12 insertions, 4 deletions
diff --git a/llvm/docs/BytecodeFormat.html b/llvm/docs/BytecodeFormat.html
index b2370eecc4b..06320a30b4f 100644
--- a/llvm/docs/BytecodeFormat.html
+++ b/llvm/docs/BytecodeFormat.html
@@ -1275,10 +1275,18 @@ field definitions, based on type:</p>
<ul>
<li><b>Bool</b>. This is written as an <a href="#uint32_vbr">uint32_vbr</a> of
value 1U or 0U.</li>
- <li><b>Signed Integers (sbyte,short,int,long)</b>. These are written as an
- <a href="#int64_vbr">int64_vbr</a> with the corresponding value.</li>
- <li><b>Unsigned Integers (ubyte,ushort,uint,ulong)</b>. These are written as
- an <a href="#uint64_vbr">uint64_vbr</a> with the corresponding value. </li>
+ <li><b>Signed Integers (sbyte,short,int,long) &le; 64 bits</b>. These are
+ written as an <a href="#int64_vbr">int64_vbr</a> with the corresponding
+ value.</li>
+ <li><b>Unsigned Integers (ubyte,ushort,uint,ulong) &le; 64 bits</b>. These
+ are written as an <a href="#uint64_vbr">uint64_vbr</a> with the corresponding
+ value. </li>
+ <li><b>Integers &gt; 64 bits</b>. 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 <a href="#uint32_vbr">uint32_vbr</a>. Each word of the value
+ is written as an <a href="#uint64_vbr">uint64_vbr</a>.</li>
<li><b>Floating Point</b>. Both the float and double types are written
literally in binary format.</li>
<li><b>Arrays</b>. Arrays are written simply as a list of
OpenPOWER on IntegriCloud