Stackless/microthreads merge news

[Christian Tismer]

Neel Krishnaswami wrote:
[unmature hype of a probable stackless Java]

> Fairly difficult, I would assume -- if there's a JIT it will almost
> certainly try to stack-allocate activation records. You'd need to
> explictly heap-allocate all that. Fortunately, Andrew Appel seems
> to believe that heap-allocation of frames can effectively compete
> with stack allocation, see:

Thanks a lot - I know these publications.

The problem is smaller. We don't need to make everything into
heaps, but we can do this at certain points. This can be the
procedure level, but it can be even coarser. The granularity
depends on what we want to switch.
Finally, I want to be able to switch what I now can switch
in CPython. In JPython, I want something similar, but this
doesn't mean to need to be able to switch every and all things
all the time.

It-is-stackless-if-it-is-better-*and*-not-slower - ly y'rs - chris

-- 
Christian Tismer             :^)   <mailto:tismer at appliedbiometrics.com>
Applied Biometrics GmbH      :     Have a break! Take a ride on Python's
Kaunstr. 26                  :    *Starship* http://starship.python.net
14163 Berlin                 :     PGP key -> http://wwwkeys.pgp.net
PGP Fingerprint       E182 71C7 1A9D 66E9 9D15  D3CC D4D7 93E2 1FAE F6DF
     where do you want to jump today?   http://www.stackless.com