From: Andi Kleen <andi@firstfloor.org>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Andi Kleen <andi@firstfloor.org>,
"H.J. Lu" <hjl.tools@gmail.com>,
Kirill Yukhin <kirill.yukhin@gmail.com>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [i386, patch, RFC] HLE support in GCC
Date: Tue, 10 Apr 2012 19:47:00 -0000 [thread overview]
Message-ID: <20120410194711.GJ17822@one.firstfloor.org> (raw)
In-Reply-To: <CAFULd4aH-4LVgNVYB4o=ZfvryKdP1mZHmWeKAcHSGgrAGHJFJA@mail.gmail.com>
> In this case, can we reverse this sentence and just emit "lock
> xacquire" for MEMMODEL_ACQUIRE and "lock xrelease" for
> MEMMODEL_RELEASE ? Do we need separate HLE_* defines or can we somehow
> recycle existing C++11 memmodel defines?
No you absolutely can't. Transactions are quite different from a normal
lock. There can be good reasons to have locks that never speculates
(e.g. if they do some operation that always aborts)
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2012-04-10 19:47 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 17:43 Uros Bizjak
2012-04-10 19:47 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-07 11:06 Kirill Yukhin
2012-03-07 11:10 ` Jakub Jelinek
2012-03-08 1:57 ` H.J. Lu
[not found] ` <CAGs3Rft_0Cs6v3AP_LH2tbbqrym5rf1A4MJ+6fn1T37=BEzrbw@mail.gmail.com>
2012-03-08 15:04 ` H.J. Lu
2012-03-08 15:09 ` Jakub Jelinek
2012-04-10 14:12 ` Kirill Yukhin
2012-04-10 14:21 ` Jakub Jelinek
2012-04-10 17:05 ` Uros Bizjak
2012-04-10 14:43 ` H.J. Lu
2012-04-10 14:44 ` Jakub Jelinek
2012-04-10 16:35 ` Andi Kleen
2012-04-10 20:00 ` H.J. Lu
2012-04-10 20:20 ` Andi Kleen
2012-04-11 10:35 ` Kirill Yukhin
2012-04-11 10:51 ` Jakub Jelinek
2012-04-11 11:40 ` Uros Bizjak
2012-04-11 13:06 ` Andi Kleen
2012-04-11 13:13 ` Jakub Jelinek
2012-04-11 13:21 ` Andi Kleen
2012-04-11 15:53 ` Kirill Yukhin
2012-04-11 16:07 ` Andi Kleen
2012-04-11 16:11 ` Jakub Jelinek
2012-04-11 16:19 ` Andi Kleen
2012-04-11 16:24 ` Jakub Jelinek
2012-04-11 16:40 ` Andi Kleen
2012-04-11 18:52 ` Jakub Jelinek
2012-04-11 21:04 ` Andi Kleen
2012-04-11 19:03 ` Uros Bizjak
2012-04-11 22:39 ` Torvald Riegel
2012-04-12 8:46 ` Kirill Yukhin
2012-04-12 9:37 ` Kirill Yukhin
2012-04-12 9:47 ` Jakub Jelinek
2012-04-12 11:36 ` Andi Kleen
2012-04-12 12:35 ` Torvald Riegel
2012-04-12 12:57 ` Andi Kleen
2012-04-12 12:22 ` Andrew MacLeod
2012-04-12 12:29 ` Jakub Jelinek
2012-04-12 12:59 ` Andi Kleen
2012-04-12 12:47 ` Andi Kleen
2012-04-12 13:23 ` Torvald Riegel
2012-04-12 13:26 ` Andi Kleen
2012-04-12 14:13 ` Kirill Yukhin
2012-04-12 18:05 ` Torvald Riegel
2012-04-13 11:40 ` Kirill Yukhin
2012-04-17 14:37 ` Sergey Ostanevich
2012-04-17 14:42 ` Andi Kleen
2012-04-18 8:22 ` Sergey Ostanevich
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=20120410194711.GJ17822@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jakub@redhat.com \
--cc=kirill.yukhin@gmail.com \
--cc=ubizjak@gmail.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).