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

[Chris Lattner]

Changes in directory llvm/docs:

BytecodeFormat.html updated: 1.12 -> 1.13

---
Log message:

Structures allow only uint
arrays allow int/uint/long/ulong


---
Diffs of the changes:  (+4 -5)

Index: llvm/docs/BytecodeFormat.html
diff -u llvm/docs/BytecodeFormat.html:1.12 llvm/docs/BytecodeFormat.html:1.13
--- llvm/docs/BytecodeFormat.html:1.12	Mon Jul  5 03:18:07 2004
+++ llvm/docs/BytecodeFormat.html	Mon Jul  5 12:55:28 2004
@@ -767,10 +767,9 @@
   for accessing a structure field and a long type index for accessing an array
   element. Consequently, it was only possible to access structures of 255 or
   fewer elements. Starting in version 1.3, this restriction was lifted. 
-  Structures must now be indexed with int or uint types. Arrays must now be 
-  indexed with long or ulong types. This requirement was needed so that LLVM
-  could compile several test cases that used large numbers of fields in their
-  structures. The consequence of this was that the bytecode format had to 
+  Structures must now be indexed with uint constants. Arrays may now be 
+  indexed with int, uint, long, or ulong typed values. 
+  The consequence of this was that the bytecode format had to 
   change in order to accommodate the larger range of structure indices.</p>
 </div>
 
@@ -812,7 +811,7 @@
   <a href="mailto:rspencer at x10sys.com">Reid Spencer</a> and 
   <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: 2004/07/05 08:18:07 $
+  Last modified: $Date: 2004/07/05 17:55:28 $
 </address>
 </body>
 </html>