From: Andi Kleen <andi@firstfloor.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
gcc-patches@gcc.gnu.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/2] Document HLE / RTM intrinsics
Date: Sun, 27 Jan 2013 21:22:00 -0000 [thread overview]
Message-ID: <20130127212206.GO30577@one.firstfloor.org> (raw)
In-Reply-To: <51056ECE.9060605@redhat.com>
On Sun, Jan 27, 2013 at 07:15:42PM +0100, Florian Weimer wrote:
> On 01/12/2013 04:28 PM, Andi Kleen wrote:
>
> >The TSX HLE/RTM intrinsics were missing documentation. Add this to the
> >manual.
>
> Are these intrinsics restricted to free-standing implementations? Or
> are these instructions designed in such a way that they work as expected
> even if the threading library uses them internally? (That would be
> quite a feat.)
They can be combined with a threading library, with some restrictions.
See the manual for details. All transactions are flattened.
http://software.intel.com/sites/default/files/m/a/b/3/4/d/41604-319433-012a.pdf
chapter 8
"restrictions" may lead to not eliding or abort, but never to
correctness problems.
Documenting all that is out of scope for the gcc manual though.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2013-01-27 21:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 15:29 Andi Kleen
2013-01-12 15:29 ` [PATCH 2/2] Support __ATOMIC_HLE_RELEASE for __atomic_clear/store_n Andi Kleen
2013-01-12 17:02 ` [PATCH 1/2] Document HLE / RTM intrinsics Bernhard Reutner-Fischer
2013-01-12 17:20 ` Andi Kleen
2013-01-14 14:44 ` Richard Biener
2013-01-14 18:22 ` Andi Kleen
2013-01-20 18:50 ` [PING] " Andi Kleen
2013-01-26 22:55 ` [PING^2] " Andi Kleen
2013-02-14 21:34 ` [PING^3] " Andi Kleen
2013-01-27 18:16 ` Florian Weimer
2013-01-27 21:22 ` Andi Kleen [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=20130127212206.GO30577@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=fweimer@redhat.com \
--cc=gcc-patches@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).