[llvm-commits] CVS: llvm/docs/LangRef.html

[Misha Brukman]

Changes in directory llvm/docs:

LangRef.html updated: 1.91 -> 1.92
---
Log message:

Hyphenate the adjective `n-bit' when used to describe values and processors


---
Diffs of the changes:  (+15 -15)

 LangRef.html |   30 +++++++++++++++---------------
 1 files changed, 15 insertions(+), 15 deletions(-)


Index: llvm/docs/LangRef.html
diff -u llvm/docs/LangRef.html:1.91 llvm/docs/LangRef.html:1.92
--- llvm/docs/LangRef.html:1.91	Mon Mar 28 14:05:48 2005
+++ llvm/docs/LangRef.html	Fri Apr 22 13:02:52 2005
@@ -513,11 +513,11 @@
         <tbody>
         <tr><th>Type</th><th>Description</th></tr>
         <tr><td><tt>void</tt></td><td>No value</td></tr>
-        <tr><td><tt>ubyte</tt></td><td>Unsigned 8 bit value</td></tr>
-        <tr><td><tt>ushort</tt></td><td>Unsigned 16 bit value</td></tr>
-        <tr><td><tt>uint</tt></td><td>Unsigned 32 bit value</td></tr>
-        <tr><td><tt>ulong</tt></td><td>Unsigned 64 bit value</td></tr>
-        <tr><td><tt>float</tt></td><td>32 bit floating point value</td></tr>
+        <tr><td><tt>ubyte</tt></td><td>Unsigned 8-bit value</td></tr>
+        <tr><td><tt>ushort</tt></td><td>Unsigned 16-bit value</td></tr>
+        <tr><td><tt>uint</tt></td><td>Unsigned 32-bit value</td></tr>
+        <tr><td><tt>ulong</tt></td><td>Unsigned 64-bit value</td></tr>
+        <tr><td><tt>float</tt></td><td>32-bit floating point value</td></tr>
         <tr><td><tt>label</tt></td><td>Branch destination</td></tr>
         </tbody>
       </table>
@@ -527,11 +527,11 @@
         <tbody>
           <tr><th>Type</th><th>Description</th></tr>
           <tr><td><tt>bool</tt></td><td>True or False value</td></tr>
-          <tr><td><tt>sbyte</tt></td><td>Signed 8 bit value</td></tr>
-          <tr><td><tt>short</tt></td><td>Signed 16 bit value</td></tr>
-          <tr><td><tt>int</tt></td><td>Signed 32 bit value</td></tr>
-          <tr><td><tt>long</tt></td><td>Signed 64 bit value</td></tr>
-          <tr><td><tt>double</tt></td><td>64 bit floating point value</td></tr>
+          <tr><td><tt>sbyte</tt></td><td>Signed 8-bit value</td></tr>
+          <tr><td><tt>short</tt></td><td>Signed 16-bit value</td></tr>
+          <tr><td><tt>int</tt></td><td>Signed 32-bit value</td></tr>
+          <tr><td><tt>long</tt></td><td>Signed 64-bit value</td></tr>
+          <tr><td><tt>double</tt></td><td>64-bit floating point value</td></tr>
         </tbody>
       </table>
     </td>
@@ -2637,7 +2637,7 @@
 specified by <i>address</i> and returns the value.  The address and return
 value must be integers, but the size is dependent upon the platform upon which
 the program is code generated.  For example, on x86, the address must be an
-unsigned 16 bit value, and the return value must be 8, 16, or 32 bits.
+unsigned 16-bit value, and the return value must be 8, 16, or 32 bits.
 </p>
 
 </div>
@@ -2681,7 +2681,7 @@
 The '<tt>llvm.writeport</tt>' intrinsic writes <i>value</i> to the I/O port
 specified by <i>address</i>.  The address and value must be integers, but the
 size is dependent upon the platform upon which the program is code generated.
-For example, on x86, the address must be an unsigned 16 bit value, and the
+For example, on x86, the address must be an unsigned 16-bit value, and the
 value written must be 8, 16, or 32 bits in length.
 </p>
 
@@ -2721,7 +2721,7 @@
 location specified by <i>pointer</i> and returns the value.  The argument must
 be a pointer, and the return value must be a
 <a href="#t_firstclass">first class</a> type.  However, certain architectures
-may not support I/O on all first class types.  For example, 32 bit processors
+may not support I/O on all first class types.  For example, 32-bit processors
 may only support I/O on data types that are 32 bits or less.
 </p>
 
@@ -2768,7 +2768,7 @@
 The '<tt>llvm.writeio</tt>' intrinsic writes <i>value</i> to the memory mapped
 I/O address specified by <i>pointer</i>.  The value must be a
 <a href="#t_firstclass">first class</a> type.  However, certain architectures
-may not support I/O on all first class types.  For example, 32 bit processors
+may not support I/O on all first class types.  For example, 32-bit processors
 may only support I/O on data types that are 32 bits or less.
 </p>
 
@@ -3015,7 +3015,7 @@
 
   <a href="mailto:sabre at nondot.org">Chris Lattner</a><br>
   <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
-  Last modified: $Date: 2005/03/28 20:05:48 $
+  Last modified: $Date: 2005/04/22 18:02:52 $
 </address>
 </body>
 </html>