maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

Describe how arbitrary precision integers are written to the bytecode. 

llvm-svn: 34719
This commit is contained in:
Reid Spencer 2007-02-28 02:33:06 +00:00
parent b5cf20c939
commit ccaec8e7c4
1 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
llvm/docs/BytecodeFormat.html
View File

@ -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