From: forsyth@caldo.demon.co.uk forsyth@caldo.demon.co.uk
Subject: [9fans] TAS
Date: Sat, 19 Jun 1999 12:52:43 +0100 [thread overview]
Message-ID: <19990619115243.56T-kLz-57R7A6yTflmAlQvNotzyZYdAjXHW4T3hjKg@z> (raw)
>>architecture for example, it seems TAS maps onto a `swap' instruction,
>> ...
>>Why implement tas() as a function, rather than do what it does inline.
it needs to use an instruction that guarantees interlock (on a multiprocessor)
and i assume `swap' does that on the sparc. the instruction needed will be
peculiar to an architecture, hence it's found in a platform-dependent
function separate from the portable code. the linkers are in a position to
inline things if need be (and do actually do some code shuffling as it is,
though not perhaps in this case -- i haven't looked).
next reply other threads:[~1999-06-19 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-19 11:52 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-06-19 15:52 pip
1999-06-19 9:20 Nigel
1999-06-18 16:55 pip
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19990619115243.56T-kLz-57R7A6yTflmAlQvNotzyZYdAjXHW4T3hjKg@z \
--to=forsyth@caldo.demon.co.uk \
/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 NNTP newsgroup(s).