RE: Using int32_t instead of IV for code

[Hong Zhang]

> If we are going to keep on doing fancy stuff with pointer arithmetic (eg
> the Alloc_Aligned/CHUNK_BASE stuff), I think we're also going to need an
> integer type which is guaranteed to be the same width as a pointer, so
> we can freely typecast between the two.

You are not supposed to do fancy stuff with code stream.
> 
> Also, if we've got a system with 64 bit IVs, are the arguments to Parrot
> opcodes going to be 32 or 64 bit? If 32 bit, is there going to be any
> way of loading a 64 bit constant?

The arguments are always 32-bit. For larger constant, such as 64-bit int,
number, bigint/bigfloat/string, you must use constant pool. There is not
much benefit to embed 64-bit value into code stream, since it is rarely
used and bloat up everything else.

Hong