From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kevin Ryde Newsgroups: gmane.lisp.guile.user Subject: Re: Some introductory docs about C level threading Date: Thu, 10 Feb 2005 07:19:22 +1100 Message-ID: <87d5v9xz91.fsf@zip.com.au> References: <6b496d191d7216e82df4e9a7afbb3168@raeburn.org> <87fz0falxl.fsf@zip.com.au> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1107981311 6205 80.91.229.2 (9 Feb 2005 20:35:11 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 9 Feb 2005 20:35:11 +0000 (UTC) Cc: guile-user@gnu.org Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Wed Feb 09 21:35:11 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1CyyXP-0001A7-1g for guile-user@m.gmane.org; Wed, 09 Feb 2005 21:34:15 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Cyylz-0001eP-QR for guile-user@m.gmane.org; Wed, 09 Feb 2005 15:49:19 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Cyyjs-0000kX-Fs for guile-user@gnu.org; Wed, 09 Feb 2005 15:47:09 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Cyyjl-0000hr-Kg for guile-user@gnu.org; Wed, 09 Feb 2005 15:47:02 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Cyyjl-0000aq-E7 for guile-user@gnu.org; Wed, 09 Feb 2005 15:47:01 -0500 Original-Received: from [61.8.0.85] (helo=mailout2.pacific.net.au) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CyyJ6-0003pf-Ew for guile-user@gnu.org; Wed, 09 Feb 2005 15:19:29 -0500 Original-Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86]) by mailout2.pacific.net.au (8.12.3/8.12.3/Debian-7.1) with ESMTP id j19KJRHn028446; Thu, 10 Feb 2005 07:19:27 +1100 Original-Received: from localhost (ppp25B5.dyn.pacific.net.au [61.8.37.181]) by mailproxy1.pacific.net.au (8.12.3/8.12.3/Debian-7.1) with ESMTP id j19KJPTu008708; Thu, 10 Feb 2005 07:19:26 +1100 Original-Received: from gg by localhost with local (Exim 3.36 #1 (Debian)) id 1CyyJ0-0000Ow-00; Thu, 10 Feb 2005 07:19:22 +1100 Original-To: Marius Vollmer In-Reply-To: (Marius Vollmer's message of "Wed, 09 Feb 2005 13:08:45 +0100") User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org X-MailScanner-To: guile-user@m.gmane.org Xref: main.gmane.org gmane.lisp.guile.user:4232 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.user:4232 Marius Vollmer writes: > > Kevin Ryde writes: > >> You can force load/stores to be exactly as given using `volatile', [...] > > How would that work exactly? Can we flag each assignment operation as > volatile, or would the SCM type need to be made volatile? Volatile marks a variable or a pointer location as possibly changing mysteriously (other threads in this case), so it'd go on pointers to SCMs and probably on global SCM vars. Newly created SCMs wouldn't need it, they're as yet unknown to other threads. > Would this be a reason to remove SCM_SMOB_OBJECT_LOC, for example, Probably not, but an application might need to think about whether it should use "volatile SCM *" instead of "SCM *". _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://lists.gnu.org/mailman/listinfo/guile-user