Hi Carl, On Tue, Mar 18, 2008 at 10:53:46AM +0100, Carl Friedrich Bolz wrote: > > - Threads using the new gc seems pretty important > > That's true, but I fear that this is a very hard (probably too hard) > task.
No, the basic task is only to ensure that threads and our new GCs can be used in the same pypy-c. This doesn't mean that the GCs should be multithreaded or even thread-safe, if we take care of only allocating objects when the GIL is held (Global Interpreter Lock). A fully multithreaded GC is step two. It would be good for RPython programs that are more freely multithreaded, like Alexander's attempt to just remove the GIL from pypy-c and not care about crashes (using explicit locks at application-level to prevent them). Getting there is more work indeed. Any student with JikesRVM MMTk experience around? :-) A bientot, Armin. _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
