At 11:26 AM +0200 6/9/02, Jerome Vouillon wrote:
>On Sat, Jun 08, 2002 at 02:34:19PM -0400, Dan Sugalski wrote:
> > Indirect function calls will take maybe 50 cycles, so I'm not worried
> > about their time. Compared to perl 5, that's fast.
>
>With a JIT compiler, this starts to be significant,
This seems like a good time to send in this patch:
It allocates the stack content memory using a buffer. This makes the stack
chunks and the memory used to hold stack contents visible to the garbage
collector. One can incrementally add to this to support copy-on-write
semantics for the chunk co
On Sat, Jun 08, 2002 at 09:59:10AM -0700, Larry Wall wrote:
> On Fri, 7 Jun 2002, Peschko, Edward wrote:
> : Let me get this straight. the grammar of Perl is reprogrammable,
> : and expressed in perl6. And a script is parsed using this grammar,
> : on the fly, hence portions of scripts could have
At 11:00 AM +0200 6/9/02, Jerome Vouillon wrote:
>On Sat, Jun 08, 2002 at 02:39:33PM -0400, Dan Sugalski wrote:
>> >Instead of using some space on the stack, co-routines can store all
>> >their local variables into their closure. Then, there is no need to
>> >swap in any context.
>>
>> You st
At 03:49 PM 6/9/2002 +0200, Jerome Vouillon wrote:
Thanks for the links and references, Jerome. I'll have a go
at digesting these. As soon as the new neural pathways
have formed I'll try to comment on where I can see us
improving our implementation. :)
-Melvin
At 04:34 PM 6/9/2002 +, [EMAIL PROTECTED] wrote:
>cvsuser 02/06/09 09:34:43
> This needs rethinking. PIOHANDLE may not be an integer, so this
> implementation is probably incorrect. For now, i'm just disabling it
> unless
> the UNIX io module is used, so that warnings aren't gener
FYI.
If anyone wants to provide a uintptr_t-equivalent for parrot, i'll happily
switch this to use it.
--Josh
--- Forwarded Message
Date:09 Jun 2002 16:44:35 -
From:[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: cvs commit: parrot/include/parrot parrot.h
cvsuser 0
On Sat, Jun 08, 2002 at 02:29:53PM -0400, Dan Sugalski wrote:
> There's more than just exception handlers going on the control stack.
> Anything that needs rolling back or undoing (like localized variables
> or scope entry) will have an undo marker put on the control stack
> that gets called wh
On Sat, Jun 08, 2002 at 03:54:06PM -0400, Melvin Smith wrote:
> At 02:36 PM 6/8/2002 -0400, Dan Sugalski wrote:
> >At 8:15 PM +0200 6/8/02, Jerome Vouillon wrote:
> >>On Sat, Jun 08, 2002 at 12:30:36PM -0400, Melvin Smith wrote:
> >>> The Java VM does this by popping values off of the local stack,
On Sat, Jun 08, 2002 at 02:34:19PM -0400, Dan Sugalski wrote:
> Indirect function calls will take maybe 50 cycles, so I'm not worried
> about their time. Compared to perl 5, that's fast.
With a JIT compiler, this starts to be significant, though.
> >A continuation can be invoked just like any o
On Sat, Jun 08, 2002 at 02:39:33PM -0400, Dan Sugalski wrote:
> >Instead of using some space on the stack, co-routines can store all
> >their local variables into their closure. Then, there is no need to
> >swap in any context.
>
> You still need to store the stack frames created since the start
On Sat, Jun 08, 2002 at 03:35:39PM -0400, Melvin Smith wrote:
> At 08:30 PM 6/8/2002 +0200, Jerome Vouillon wrote:
> >Instead of using some space on the stack, co-routines can store all
> >their local variables into their closure. Then, there is no need to
> >swap in any context.
>
> We have to
12 matches
Mail list logo
