Guilhem,
> Yes. Correct. (Look at jit3/slots.h and jit/slots.h)
jit/slots.h does not have anything describing the info I am interested
in, however, jit3/slots.h does.
How closely does kaffe.def follow this convention? FALOAD uses method
load_offset_scaled_float(stack_float(1), stack(1),
stack(0
Guilhem Lavaux wrote:
Michael Franz wrote:
Hi,
I have been going over kaffe.def and slots.h to figure out how the
interpreter works. I understand what the slots.h macros are doing
(stack, pop, push, ) but I don't understand what the logical
difference is amoung rstack, wstack and stack? I am
Michael Franz wrote:
Hi,
I have been going over kaffe.def and slots.h to figure out how the
interpreter works. I understand what the slots.h macros are doing
(stack, pop, push, ) but I don't understand what the logical
difference is amoung rstack, wstack and stack? I am thinking Read
stack, W
Hi,
I have been going over kaffe.def and slots.h to figure out how the
interpreter works. I understand what the slots.h macros are doing
(stack, pop, push, ) but I don't understand what the logical
difference is amoung rstack, wstack and stack? I am thinking Read
stack, Write stack and just
