[slime-devel] CVS slime

Helmut Eller heller at common-lisp.net
Mon Jun 20 14:39:45 UTC 2011

* Martin Simmons [2011-06-20 12:01] writes:

>>>>>> On Mon, 20 Jun 2011 09:02:40 +0200, Helmut Eller said:
>> Alternatively you also copy the cache, update the copy, and finally
>> store the copy with a single setf into the shared location.  That would
>> be thread safe enough.
> I think that strategy requires memory barriers for safety.

Read-after-write consistency is not needed in this case.  The next
thread will recognize that his copy is obsolete and will compute the
same result.  No harm done; just some redundant computations.


More information about the slime-devel mailing list