At 01:07 PM 11/23/2003 +0100, Leopold Toetsch wrote:
Melvin Smith <[EMAIL PROTECTED]> wrote:
> At 11:34 PM 11/22/2003 +0100, Leopold Toetsch wrote:
> Ix regs are for:
> 1) Fast integer stuff
> 2) Iteration (increment variables)
> 3) Conditional checks
> 4) Branching and holding addresses
> 5) Index
Melvin Smith <[EMAIL PROTECTED]> wrote:
> At 11:34 PM 11/22/2003 +0100, Leopold Toetsch wrote:
>>The concept of having INTVAL constants inside the opcodes is
>>wrong from a general POV. Please have a look at e.g jit/arm/ what
>>immediate constants are requiring as work arounds.
> I'm not aware of
At 10:14 PM 11/22/2003 -0500, Melvin Smith wrote:
At 11:34 PM 11/22/2003 +0100, Leopold Toetsch wrote:
Melvin Smith <[EMAIL PROTECTED]> wrote:
> to override it, it is not supported to choose INTVAL > OPCODE, though
> the inverse is. So storing it in the header is probably redundant, unless
> we cha
At 11:34 PM 11/22/2003 +0100, Leopold Toetsch wrote:
Melvin Smith <[EMAIL PROTECTED]> wrote:
> Parrot currently assumes INTVAL size == OPCODE size because
> both get configured as the same integral type, although you can choose
> to override it, it is not supported to choose INTVAL > OPCODE, thoug
Melvin Smith <[EMAIL PROTECTED]> wrote:
> Parrot currently assumes INTVAL size == OPCODE size because
> both get configured as the same integral type, although you can choose
> to override it, it is not supported to choose INTVAL > OPCODE, though
> the inverse is. So storing it in the header is pr
At 12:13 PM 11/22/2003 +, you wrote:
* write intval size into PBC header
Leo, I know this is a first cut at freeze/thaw, and I'm happy you've
done it. Let me make some comments to you and Dan.
I'm pretty sure Dan and I discussed this when I was reworking bytecode
to be portable last year, but
