From: "Paul D. DeRocco" <pderocco@ix.netcom.com>
To: "eCos Discuss" <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Lightweight C++ multithreaded exceptions
Date: Tue, 24 May 2005 09:13:00 -0000 [thread overview]
Message-ID: <NEBBKHCFDGIGIJEHDJFCAEACPAAA.pderocco@ix.netcom.com> (raw)
In-Reply-To: <42921638.1090405@jifvik.org>
> From: Jonathan Larmour
>
> libstdc++ has atomicity primitives for some CPUs, including x86, m68k,
> mips, powerpc and SPARC. Notably it doesn't include ARM, probably because
> at least on some ARM architecture versions it isn't possible. I
> don't know
> for definite about recent ARM architecture versions.
ARM7 and later have a swap byte or word, which is locked.
--
Ciao, Paul D. DeRocco
Paul mailto:pderocco@ix.netcom.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2005-05-23 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 9:13 Øyvind Harboe
2005-05-23 12:52 ` Jerome Souquieres
2005-05-23 13:25 ` Øyvind Harboe
2005-05-24 8:48 ` Jonathan Larmour
2005-05-24 9:01 ` Øyvind Harboe
2005-05-24 9:13 ` Paul D. DeRocco [this message]
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=NEBBKHCFDGIGIJEHDJFCAEACPAAA.pderocco@ix.netcom.com \
--to=pderocco@ix.netcom.com \
--cc=ecos-discuss@ecos.sourceware.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).