From: Frode Vatvedt Fjeld <fro...@cs.uit.no>
Date: 11 Mar 2007 20:38:22 +0100
Local: Sun, Mar 11 2007 3:38 pm
Subject: Re: Switch from SBCL to Erlang backend due to scalability issues(GC).
> > "bradb" <brad.beveri...@gmail.com> writes:Well, the resolution would typically be finer than a function. A
> > > It seems to me that it would be possible for the compiler to
> > > track Lisp/non-Lisp registers if it were required. For example,
> > > you could store a word on the stack that had status bits
> > > determining what a register was used for. Then when the GC
> > > scavenged the stack it would look at this word and choose which
> > > saved values were actually objects. I'm curious if the scheme
> > > I've just outlined would actually work?
> On Mar 7, 3:36 pm, Frode Vatvedt Fjeld <fro...@cs.uit.no> wrote:
(thread-)global variable holds the register usage status (for example
there is one bit per register, indicating GC-root on/off). The
compiler will know whether it requires non-standard register usage,
and when required it emits instructions to set and re-set the
In my particular system (www.common-lisp.net/project/movitz) there are
The same concept can be used for stack-frames, but here there would be
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.