From: "Boehm, Hans" <hans.boehm@hp.com>
To: Bryce McKinlay <bmckinlay@gmail.com>, GCC Java <java@gcc.gnu.org>
Cc: Ivan Maidanski <ivmai@mail.ru>
Subject: RE: [Gc] Re: boehm-gc merge for GCC
Date: Tue, 27 Nov 2012 01:09:00 -0000 [thread overview]
Message-ID: <A3E67C2071F49C4CBC4F17E6D77CDDD23694F5A3@G9W0725.americas.hpqcorp.net> (raw)
In-Reply-To: <CALUNu-pkdM8xXrJoCuJTW41zn0BiHntQLzC8=sLuHR2DbHVjbw@mail.gmail.com>
>
> > - bdwgc now depends on another library (libatomic-ops). Shouldn't GCC
> > be able to use it's atomic builtins for some supported targets at
> > least?
>
>
> Yes, but it sounds like far more effort than its worth to go and change
> it
> just for the sake of using builtins. Maybe libatomic-ops itself could
> be
> made to use the builtins when available.
>
Libatomic_ops should eventually be configurable to just use C11/C++11 atomic operations. That hasn't happened yet, but should be fairly easy. Or, if we wait long enough, we could just use the C11 primitves directly. Historically libatomic-ops preceded and influenced the C11/C++11 interface, but the C11/C++11 interface is a much better design (another iteration, a lot more careful thought by many more people, etc.)
Hans
next prev parent reply other threads:[~2012-11-27 1:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1353097280.505328435@f161.mail.ru>
[not found] ` <50A67667.7020600@ubuntu.com>
[not found] ` <CAF1jjLucRudE2a3gCZq6erkJKfs1nC+DicM+4f4moXJ5HPy9g@mail.gmail.com>
[not found] ` <1353099257.140499471@f123.mail.ru>
[not found] ` <CAF1jjLsA1nzLaJejMiAfzqZZ8btw37n0B3H7_qz-UrLvNQGqzA@mail.gmail.com>
[not found] ` <50A6EE27.4000605@ubuntu.com>
[not found] ` <50ABADE0.9000305@redhat.com>
[not found] ` <50B385C5.6010004@ubuntu.com>
[not found] ` <CALUNu-p3muXCwGV9sRSF550EvyM2=f0=mbEzDEhtf=BdhUJKMQ@mail.gmail.com>
2012-11-26 17:03 ` Bryce McKinlay
2012-11-26 17:50 ` Andrew Haley
2012-11-27 1:09 ` Boehm, Hans [this message]
2012-12-01 20:50 ` Matthias Klose
2012-12-02 2:51 ` Matthias Klose
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=A3E67C2071F49C4CBC4F17E6D77CDDD23694F5A3@G9W0725.americas.hpqcorp.net \
--to=hans.boehm@hp.com \
--cc=bmckinlay@gmail.com \
--cc=ivmai@mail.ru \
--cc=java@gcc.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).