From: Dan Kegel <dank@kegel.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Proposal for a userspace "architecture portability" library
Date: Sat, 04 Dec 2004 22:18:59 -0800 [thread overview]
Message-ID: <41B2A853.9050504@kegel.com> (raw)
Roland McGrath <roland () redhat ! com> wrote:
>> I don't think glibc exports any atomic operations.
>
>That is true. But it does have implementations in bits/atomic.h for many
>processors, and that is under the LGPL.
Interesting. This seems to be new as of glibc-2.3.3.
(glibc-2.3.2 had implementations of all sorts of things,
spinlocks even, but they were all internal.)
gcc's libstdc++ also exports an atomicity.h
(in e.g. /usr/include/c++/3.4.2/bits/atomicity.h).
gcc's libjava also has its own set of lock primitives
(buried in a file named locks.h).
It would be quite the engineering feat to demonstrate
a gcc/glibc toolchain actually using your proposed
portability layer and demonstrate zero loss of performance.
Even that might not be enough to convince the glibc
maintainer to use it...
- Dan
--
Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
next reply other threads:[~2004-12-05 7:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 6:18 Dan Kegel [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-05 0:53 Proposal for a userspace "architecture portability" library Paul Mackerras
2004-12-05 1:08 ` Robert Love
2004-12-05 1:47 ` Paul Mackerras
2004-12-05 2:10 ` Kevin P. Fleming
2004-12-05 3:51 ` Roland McGrath
2004-12-05 2:40 ` H. Peter Anvin
2004-12-05 2:44 ` Benjamin Herrenschmidt
2004-12-05 4:06 ` Kevin P. Fleming
2004-12-05 18:12 ` Alan Cox
2004-12-05 19:48 ` Joseph Seigh
2004-12-05 23:29 ` Joel Becker
2004-12-06 9:42 ` Adrian 'Dagurashibanipal' von Bidder
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=41B2A853.9050504@kegel.com \
--to=dank@kegel.com \
--cc=linux-kernel@vger.kernel.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