Structures allow only uint
arrays allow int/uint/long/ulong llvm-svn: 14629
This commit is contained in:
parent
4e0352d8c7
commit
8aa561992c
|
@ -767,10 +767,9 @@ describes the differences between that version and the one that <i>follows</i>
|
||||||
for accessing a structure field and a long type index for accessing an array
|
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
|
element. Consequently, it was only possible to access structures of 255 or
|
||||||
fewer elements. Starting in version 1.3, this restriction was lifted.
|
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
|
Structures must now be indexed with uint constants. Arrays may now be
|
||||||
indexed with long or ulong types. This requirement was needed so that LLVM
|
indexed with int, uint, long, or ulong typed values.
|
||||||
could compile several test cases that used large numbers of fields in their
|
The consequence of this was that the bytecode format had to
|
||||||
structures. The consequence of this was that the bytecode format had to
|
|
||||||
change in order to accommodate the larger range of structure indices.</p>
|
change in order to accommodate the larger range of structure indices.</p>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue