From: Kevin Ryde <user42@zip.com.au>
Cc: guile-user@gnu.org
Subject: Re: Fetch-and-store for PowerPC... and more!
Date: Thu, 17 Mar 2005 10:26:39 +1100 [thread overview]
Message-ID: <87br9j895c.fsf@zip.com.au> (raw)
In-Reply-To: <87wts8rn7b.fsf@laas.fr> (Ludovic Courtès's message of "Wed, 16 Mar 2005 09:48:08 +0100")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
>
> The generic
> version of `FETCH_STORE' relies on `scm_mutex_lock ()' and
> `scm_mutex_unlock ()' which are not (yet) implemented.
Actually, they were implemented but then disappeared. Recent breakage
:-).
> + Note: look
> + at the `always_swap ()' function is Glibc's `atomicity.h' in the `sysdeps'
> + directory. */
Looks like that's changed in the latest and greatest glibc, now
bits/atomic.h and __arch_atomic_whatever().
> +#if defined (__GNUC__) && defined (__powerpc__) && SIZEOF_SCM_T_BITS == 4
> +
> +/* On 32-bit PowerPC arches, we use the `lwarx' ("load word and reserve,
> + indexed") and `stwcx.' ("store word conditional, indexed") instructions.
No need to describe instructions. (But crib notes on the reservation
mechanism for single or multi cpus is fine.)
> + asm ("\n1:\n" \
I think "1:" is a gas-ism, it might not work on aix and macos. But
dunno if guile actually runs at all on those systems at the moment.
> + : "=&r" (fet) \
> + : "r" (mem), "r" (sto)); \
I think "mem" should be in the outputs too, since it's changed.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-03-16 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 8:48 Fetch-and-store for PowerPC... and more! Ludovic Courtès
2005-03-16 23:26 ` Kevin Ryde [this message]
2005-03-17 8:29 ` Ludovic Courtès
2005-03-17 20:48 ` Kevin Ryde
2005-03-18 9:26 ` 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=87br9j895c.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).