From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Andy Lutomirski <luto@kernel.org>,
Uros Bizjak <uros_bizjak1@t-2.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Uros Bizjak <ubizjak@gmail.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: ASM flags in general
Date: Mon, 27 Jul 2015 17:03:08 -0700 [thread overview]
Message-ID: <9F16C950-32F0-4DC0-9B33-CD1288529C9A@zytor.com> (raw)
In-Reply-To: <CALCETrW0SM=4zLM3S3FwYjYJTeAcGrkkP+bzYP-KSpFW9QK1rg@mail.gmail.com>
There are certainly applications. That just isn't one of them.
On July 27, 2015 4:58:29 PM PDT, Andy Lutomirski <luto@amacapital.net> wrote:
>On Mon, Jul 27, 2015 at 4:56 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> Sure... but now you have to wrap things in stac/clac. I'm not sure I
>see the point since the code is already pretty much optimal.
>
>Ick. I forgot about that.
>
>It would benefit all the users who aren't using the _ex functions,
>though. And, if there are enough of those, it just might be worth
>trying to postprocess object files to collapse adjacent stac and clac
>instances, or just to teach the alternatives code to nop them out if
>they're redundant.
>
>--Andy
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2015-07-28 0:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 17:48 [PATCH v2] x86: Introduce ASM flags to bitops Uros Bizjak
2015-07-27 19:04 ` ASM flags in general H. Peter Anvin
2015-07-27 20:01 ` Uros Bizjak
2015-07-27 21:14 ` H. Peter Anvin
2015-07-27 20:38 ` Andy Lutomirski
2015-07-27 21:04 ` H. Peter Anvin
2015-07-27 22:43 ` Andy Lutomirski
[not found] ` <BFA94A6B-8E68-4990-8737-F1F470D47F6A@zytor.com>
2015-07-27 23:36 ` Andy Lutomirski
[not found] ` <E2EE4512-30B2-4E73-B91A-DC1A9AA0AF6C@zytor.com>
2015-07-27 23:49 ` Andy Lutomirski
2015-07-27 23:56 ` H. Peter Anvin
2015-07-27 23:58 ` Andy Lutomirski
2015-07-28 0:03 ` H. Peter Anvin [this message]
2015-07-28 0:35 ` H. Peter Anvin
2015-07-28 0:41 ` Andy Lutomirski
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=9F16C950-32F0-4DC0-9B33-CD1288529C9A@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=ubizjak@gmail.com \
--cc=uros_bizjak1@t-2.net \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®