On Wednesday 20 November 2002 04:41, Leopold Toetsch wrote: > Or praeprocessor magic, redifining the Parrot_jit_ops to Parrot_jit_native
OK. > > I just committed a renaming for the ppc. > > and others in the meantime - good. > Are these _load & _store different or will they just become _mov. (The > displacement-suffix is IMHO not needed on the surface. True true.... I'll fix that now. > > I'm thinking of a structure like this: > generic.jit ... 3 operand machine with op_r_r_r ... op_m_m_m > risc.jit ... 3 register machine, 2 scratch for memory ops > cisc.jit ... 2 register machine, 1 scratch > $arch.jit ... overriding if necessary and when present > > generic.jit implements the register MAPping and could probably be > autogenerated from core.ops. > risc.jit provides macros for preparing the scratch registers for the > memory operands, cisc.jit similar. > $arch.jit could implement anomalies like i386 shift ops. > I don't really know if we should spent too much time on this instead of creating an intermediate language to write opcodes on it. Daniel Grunblatt.
