Re: One more thing...

2004-06-01 Thread Piers Cawley
Leopold Toetsch <[EMAIL PROTECTED]> writes: > Piers Cawley wrote: >> But under this scheme, the implementing function will have to do a >> saveall for every function it calls because it doesn't know what >> registers its caller cares about. And you're almost certainly going >> to want to call othe

[perl #29994] [BUG] "loadlib $P0, varname" not working correctly

2004-06-01 Thread via RT
# New Ticket Created by Jens Rieks # Please include the string: [perl #29994] # in the subject line of all future correspondence about this issue. # http://rt.perl.org:80/rt3/Ticket/Display.html?id=29994 > % cat error.imc .sub _main @MAIN .local string na123me na123me = "/foo" lo

Re: Layering PMCs

2004-06-01 Thread Aaron Sherman
On Sat, 2004-05-29 at 15:29, Dan Sugalski wrote: > The problem with the first scheme is that anything that has a handle > on the PMC will not get the new layers. Not a good thing. I like the first scheme. The question that comes up is: when does something get layered? That is: if I have code th

Morph for fun and profit

2004-06-01 Thread Dan Sugalski
Okay, since I was asked, and I'm starting to hit a need for it in general, I want to address morph, and some of its ramifications. And limitations, as it seems like it's only a partial solution We had issues way back about this and we worked 'em out, at least to some extent. Now that I'm diggin

Re: JIT problem on Cygwin revisited

2004-06-01 Thread Joshua Gatcomb
I thought I had already replied to this but I don't seem to see it in the archive anywhere. --- Leopold Toetsch <[EMAIL PROTECTED]> wrote: > I think next step would need to review Cygwin math > lib sources and trace > into the library. Nasty. Parrot doesn't use GMP right? So the math library in

Re: One more thing...

2004-06-01 Thread Leopold Toetsch
Dan Sugalski <[EMAIL PROTECTED]> wrote: > If you want to go back to a frame pointer style of register stack > access, that's doable, but that's the way it was in the beginning and > the performance penalties in normal code outweighed the savings in > stack pushes. JITted memory access through the

Re: JIT problem on Cygwin revisited

2004-06-01 Thread Leopold Toetsch
Joshua Gatcomb <[EMAIL PROTECTED]> wrote: > Well, it only happens under JIT for the following > functions (identical code for atan works fine): > cosh, sinh, tanh, sech, exp, pow > It only happens if there are two set N# prior to the > function where # is two different numbers > N0 = 1 > N1 = 1