From: Kevin Ryde <user42@zip.com.au>
Cc: guile-user@gnu.org
Subject: Re: Some introductory docs about C level threading
Date: Thu, 10 Feb 2005 07:19:22 +1100 [thread overview]
Message-ID: <87d5v9xz91.fsf@zip.com.au> (raw)
In-Reply-To: <lj7jliszoy.fsf@troy.dt.e-technik.uni-dortmund.de> (Marius Vollmer's message of "Wed, 09 Feb 2005 13:08:45 +0100")
Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:
>
> Kevin Ryde <user42@zip.com.au> 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
next prev parent reply other threads:[~2005-02-09 20:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 18:29 Some introductory docs about C level threading Marius Vollmer
2005-01-21 21:20 ` Neil Jerram
2005-01-24 19:23 ` Marius Vollmer
2005-02-15 4:11 ` Robert Uhl
2005-01-22 12:37 ` tomas
2005-01-24 19:28 ` Marius Vollmer
2005-01-25 9:06 ` tomas
2005-01-25 15:58 ` Rob Browning
2005-01-25 16:01 ` Rob Browning
2005-01-26 9:05 ` tomas
2005-02-01 16:01 ` Marius Vollmer
2005-02-02 9:31 ` tomas
2005-02-02 13:18 ` Marius Vollmer
2005-02-02 13:47 ` tomas
2005-01-23 23:34 ` Kevin Ryde
2005-01-24 19:31 ` Some new reference docs about initialization Marius Vollmer
2005-01-24 20:27 ` Andreas Rottmann
2005-01-24 22:00 ` Marius Vollmer
2005-02-01 17:37 ` Some introductory docs about C level threading Ken Raeburn
2005-02-01 23:40 ` Kevin Ryde
2005-02-02 0:38 ` Ken Raeburn
2005-02-07 0:48 ` Kevin Ryde
2005-02-08 21:45 ` Ken Raeburn
2005-02-09 12:17 ` Marius Vollmer
2005-02-09 20:26 ` Kevin Ryde
2005-02-10 11:36 ` Marius Vollmer
2005-02-09 12:13 ` Marius Vollmer
2005-02-09 18:10 ` Ken Raeburn
2005-02-10 12:05 ` Marius Vollmer
2005-02-10 19:59 ` Ken Raeburn
2005-02-09 12:08 ` Marius Vollmer
2005-02-09 16:33 ` Doug Evans
2005-02-10 11:15 ` Marius Vollmer
2005-02-09 20:19 ` Kevin Ryde [this message]
2005-02-09 12:04 ` Marius Vollmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d5v9xz91.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).