From: Peter Bergner <bergner@vnet.ibm.com>
To: Richard Henderson <rth@redhat.com>, Torvald Riegel <triegel@redhat.com>
Cc: GCC <gcc@gcc.gnu.org>, Bin Fan <bin.x.fan@oracle.com>
Subject: Re: -mcx16 vs. not using CAS for atomic loads
Date: Tue, 24 Jan 2017 21:30:00 -0000 [thread overview]
Message-ID: <8e49371d-36eb-7cae-355b-849c94de4302@vnet.ibm.com> (raw)
In-Reply-To: <9892f3cf-3b6e-e280-d243-f3c36f685d42@redhat.com>
On 1/24/17 3:06 PM, Richard Henderson wrote:
> The only possible concern I see might be with simulators that force HTM
> failure, for the purpose of forcibly testing fallback paths. I guess we'd have
> to continue to fall back to the lock path for that case.
IIRC, this was the path that valgrind was going to use all of the time,
because actually implementing the HTM instructions was too hard.
Peter
next prev parent reply other threads:[~2017-01-24 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 18:23 Torvald Riegel
2017-01-20 17:55 ` Richard Henderson
2017-01-24 9:08 ` Torvald Riegel
2017-01-24 21:06 ` Richard Henderson
2017-01-24 21:30 ` Peter Bergner [this message]
2017-01-25 11:10 ` Torvald Riegel
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=8e49371d-36eb-7cae-355b-849c94de4302@vnet.ibm.com \
--to=bergner@vnet.ibm.com \
--cc=bin.x.fan@oracle.com \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.com \
--cc=triegel@redhat.com \
/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).