Re: JIT and platforms warning

2004-10-29 Thread Leopold Toetsch
Leopold Toetsch [EMAIL PROTECTED] wrote: arm, mips, and sun4 JIT platforms need definitely some work to even keep up with the current state of the JIT interface. That's actually wrong - sorry. Sun4 JIT is fairly complete and is up to date and should't have been in above sentence. I've messed

Re: [PATCH] Re: JIT and platforms warning

2004-10-24 Thread Leopold Toetsch
Jeff Clites [EMAIL PROTECTED] wrote: On Oct 23, 2004, at 4:20 AM, Leopold Toetsch wrote: Jeff Clites [EMAIL PROTECTED] wrote: See attached the patch, plus the new asm.s file. Doesn't run, segfaults on even mops.pasm - please check. I can't reproduce that here; parrot -j works for me

Re: [PATCH] Re: JIT and platforms warning

2004-10-24 Thread Leopold Toetsch
Jeff Clites [EMAIL PROTECTED] wrote: On Oct 23, 2004, at 3:42 AM, Leopold Toetsch wrote: We were allocating the volatile float registers first (or, only)--so Cset_s_sc was blowing away an N-register, even with only one in use. That's why I was surprised there weren't more failures. Yes. As

[PATCH] Re: JIT and platforms warning

2004-10-23 Thread Jeff Clites
On Oct 22, 2004, at 3:57 AM, Leopold Toetsch wrote: Jeff Clites wrote: On Oct 22, 2004, at 1:01 AM, Leopold Toetsch wrote: [JIT changes] I just finished tracking down the source of a couple of JIT test failures on PPC--due to recent changes but only indirectly related, and pointing out things

Re: [PATCH] Re: JIT and platforms warning

2004-10-23 Thread Leopold Toetsch
Jeff Clites [EMAIL PROTECTED] wrote: See attached the patch, plus the new asm.s file. Doesn't run, segfaults on even mops.pasm - please check. JEff leo

Re: [PATCH] Re: JIT and platforms warning

2004-10-23 Thread Leopold Toetsch
Jeff Clites [EMAIL PROTECTED] wrote: Yep, that was the core of the issue. There's no free lunch--if we use the nonvolatile registers, we need to preserve/restore them in begin/end, but if we use the volatile registers, we need to preserve them across function calls (incl. normal op calls).

Re: [PATCH] Re: JIT and platforms warning

2004-10-23 Thread Jeff Clites
On Oct 23, 2004, at 4:20 AM, Leopold Toetsch wrote: Jeff Clites [EMAIL PROTECTED] wrote: See attached the patch, plus the new asm.s file. Doesn't run, segfaults on even mops.pasm - please check. I can't reproduce that here; parrot -j works for me with examples/{benchmarks,assembly}/mops.pasm, and

Re: [PATCH] Re: JIT and platforms warning

2004-10-23 Thread Jeff Clites
On Oct 23, 2004, at 3:42 AM, Leopold Toetsch wrote: Jeff Clites [EMAIL PROTECTED] wrote: Yep, that was the core of the issue. There's no free lunch--if we use the nonvolatile registers, we need to preserve/restore them in begin/end, but if we use the volatile registers, we need to preserve them

Re: JIT and platforms warning

2004-10-22 Thread Jeff Clites
On Oct 22, 2004, at 1:01 AM, Leopold Toetsch wrote: [JIT changes] I just finished tracking down the source of a couple of JIT test failures on PPC--due to recent changes but only indirectly related, and pointing out things which needed fixing anyway (float register preservation issues). I'll

Re: JIT and platforms warning

2004-10-22 Thread Leopold Toetsch
Jeff Clites wrote: On Oct 22, 2004, at 1:01 AM, Leopold Toetsch wrote: [JIT changes] I just finished tracking down the source of a couple of JIT test failures on PPC--due to recent changes but only indirectly related, and pointing out things which needed fixing anyway (float register