From: Richard Henderson <rth@redhat.com>
To: Andrew MacLeod <amacleod@redhat.com>
Cc: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>,
hp@axis.com, gcc-patches@gcc.gnu.org,
libstdc++@gcc.gnu.org, Benjamin Kosnik <bkoz@redhat.com>
Subject: Re: cxx-mem-model merge [6 of 9] - libstdc++-v3
Date: Mon, 07 Nov 2011 16:32:00 -0000 [thread overview]
Message-ID: <4EB80704.90505@redhat.com> (raw)
In-Reply-To: <4EB7EEDF.1040103@redhat.com>
On 11/07/2011 06:44 AM, Andrew MacLeod wrote:
> rth: __sync_lock_test_and_set_1 could be provided by libgcc if the
> OS has hooks in it to provide functionality... How can we tell when
> compiling a C++ program whether that is going to be an unresolved
> external or whether libgcc is going to provide it? I know you have a
> pending patch for libgcc support fo the __atomics, but Im unsure how
> we check this from the compiler
In the pending patch, several of the direct_optabs get transformed
to normal optabs, and have the opportunity to have their libcall
fields filled in.
At which point one checks both optab_handler and optab_libcall for
the availability of the feature.
r~
next prev parent reply other threads:[~2011-11-07 16:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 23:52 Andrew MacLeod
2011-11-04 18:17 ` Jeff Law
2011-11-04 18:53 ` Andrew MacLeod
2011-11-07 0:54 ` Hans-Peter Nilsson
2011-11-07 4:48 ` Andrew MacLeod
2011-11-07 11:36 ` Hans-Peter Nilsson
2011-11-07 14:41 ` Andrew MacLeod
2011-11-07 14:56 ` Andrew MacLeod
2011-11-07 15:38 ` Hans-Peter Nilsson
2011-11-07 16:28 ` Joseph S. Myers
2011-11-07 17:24 ` Andrew MacLeod
2011-11-07 17:43 ` Hans-Peter Nilsson
2011-11-07 18:27 ` Andrew MacLeod
2011-11-08 6:45 ` Hans-Peter Nilsson
2011-11-08 13:43 ` Andrew MacLeod
2011-11-11 17:49 ` Benjamin Kosnik
2011-11-11 17:56 ` Andrew MacLeod
2011-11-11 21:07 ` Hans-Peter Nilsson
2011-11-11 23:34 ` Torvald Riegel
2011-11-11 20:27 ` Hans-Peter Nilsson
2011-11-07 16:32 ` Richard Henderson [this message]
2011-11-08 20:22 ` Hans-Peter Nilsson
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=4EB80704.90505@redhat.com \
--to=rth@redhat.com \
--cc=amacleod@redhat.com \
--cc=bkoz@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hans-peter.nilsson@axis.com \
--cc=hp@axis.com \
--cc=libstdc++@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).