Re: [RFC] unified core.jit

2002-11-20 Thread Daniel Grunblatt
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

Re: [RFC] unified core.jit

2002-11-19 Thread Leopold Toetsch
Daniel Grunblatt wrote: On Tuesday 19 November 2002 11:54, Leopold Toetsch wrote: Daniel Grunblatt wrote: what if we just don't want to implement that opcode in this specific architecture? Prefered: provide a native function doing the e.g. "div" and call this function from within the emi

Re: [RFC] unified core.jit

2002-11-19 Thread Nicholas Clark
On Tue, Nov 19, 2002 at 03:40:33PM -0300, Daniel Grunblatt wrote: > On Tuesday 19 November 2002 11:54, Leopold Toetsch wrote: > > We could do it like parrot (dest, src, src) too, but I want really a > > unique naming convention. > > > > leo > > Cool, let's do it like parrot. Good call. I think

Re: [RFC] unified core.jit

2002-11-19 Thread Daniel Grunblatt
On Tuesday 19 November 2002 11:54, Leopold Toetsch wrote: > Daniel Grunblatt wrote: > > > The problem is when you want to implement an opcode like div, which is > > easy in ppc but not in arm ideas? > > I don't know arm, but this belongs to jit_emit.h, how it's done there is > a different issue

Re: [RFC] unified core.jit

2002-11-19 Thread Leopold Toetsch
Daniel Grunblatt wrote: I would do a cisc.jit and a risc.jit to avoid the #ifdef forest. Good idea. The problem is when you want to implement an opcode like div, which is easy in ppc but not in arm ideas? I don't know arm, but this belongs to jit_emit.h, how it's done there is a dif

Re: [RFC] unified core.jit

2002-11-19 Thread Daniel Grunblatt
I would do a cisc.jit and a risc.jit to avoid the #ifdef forest. The problem is when you want to implement an opcode like div, which is easy in ppc but not in arm ideas? I was sort of going in that direction, mips/core.jit is almost like ppc/core.jit (If everything is on schedule I'll find s

[RFC] unified core.jit

2002-11-19 Thread Leopold Toetsch
Currently all architecures have there own core.jit. These are very similar, e.g. checking for MAPped registers, but differ depending on the processor architecure: basically we have 3 register machines (alpha, arm, ppc, sparc) and a 2 register machine (i386). My proposal is to write a universal cor