On Mar 7, 2006, at 23:44, Jonathan Worthington wrote:
The register mapping rules would be something like:
- Lx occupies registers I(2x, 2x+1) - this is compile time,
that is 'L1' prevents 'I2' and 'I3' from being assigned by the
register allocator
- the runtime mapping isn't portable due to endianess and sizeof types
'L1' might be 'I1' on 64-bit arch or (I2,I3) or (I3,I2) on 32-bit
arch
Yup, and I really, really don't like the idea of making our bytecode
format non-portable. Part of the point of having a VM is portability,
right?
The described mapping doesn't have any PBC portability issues AFAIK. If
'L' is mapping to 'I' or not is chosen at runtime.
leo
