Re: Locks and threads

Linas Vepstas writes: > An alternative idea is to try to apply some principles from > functional programming, e.g. "copy on write" (COW): when > the obarray needs to be updated, make a copy of it. Any > readers in other threads continue to safely use the > original version. When the new obarray i

Re: Locks and threads

2009/3/11 Neil Jerram : > Neil Jerram writes: > >> # >> # >> ERROR: ERROR: Unbound variable: x1-100499 >> Unbound variable: define >> ERROR: Unbound variable: x4-100596 >> ERROR: Unbound variable: define >> ERROR: Unbound variable: define >> ERROR: Unbound variable: define >> guile-define test cas

Re: Locks and threads

Neil Jerram writes: > # > # > ERROR: ERROR: Unbound variable: x1-100499 > Unbound variable: define > ERROR: Unbound variable: x4-100596 > ERROR: Unbound variable: define > ERROR: Unbound variable: define > ERROR: Unbound variable: define > guile-define test case: good-bye! > test-define-race: 2 e

Re: Locks and threads

Neil Jerram writes: >> next it's on to the real problem, threadsafe define. > > I've been running Linas's define-race test program, and hitting the > `throw from within critical section' quite a lot. [...] After the patch that I posted yesterday, we finally get to the real problem. I've tried t

Re: vm status update

Hi Neil, On Sun 08 Mar 2009 12:49, Neil Jerram writes: > Andy Wingo writes: > >> * Much more source information propagates through the compiler and >> into the metadata now. > > How much of this is compiler-specific? Does some of it also apply to > old-style reading and interpreting? No

Re: GC brokenness in `master'

Hi Neil, Neil Jerram writes: > l...@gnu.org (Ludovic Courtès) writes: >> After some manual bisecting, I found the offending commit (dated >> 2008-08-16): >> >> >> http://git.savannah.gnu.org/cgit/guile.git/commit/?id=82ae1b8eb3413e6be6bd2aa032986fc7782e85ac > > But presumably this doesn't ma