From: Ingo Molnar <mingo@kernel.org>
To: Uros Bizjak <uros_bizjak1@t-2.net>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Uros Bizjak <ubizjak@gmail.com>
Subject: Re: [PATCH] x86: Introduce ASM flags to bitops
Date: Mon, 27 Jul 2015 17:40:35 +0200 [thread overview]
Message-ID: <20150727154035.GA18213@gmail.com> (raw)
In-Reply-To: <1437869262-3211-1-git-send-email-uros_bizjak1@t-2.net>
* Uros Bizjak <uros_bizjak1@t-2.net> wrote:
> From: Uros Bizjak <ubizjak@gmail.com>
>
> This patch introduces GCC ASM flags to bitops. Instead of e.g.
>
> 136d7: 48 0f a3 3d 00 00 00 bt %rdi,0x0(%rip)
> 136de: 00
> 136df: 19 ff sbb %edi,%edi
> 136e1: 85 ff test %edi,%edi
> 136e3: 0f 95 c0 setne %al
>
> following code is generated:
>
> 13767: 48 0f a3 3d 00 00 00 bt %rdi,0x0(%rip)
> 1376e: 00
> 1376f: 0f 92 c0 setb %al
>
> Similar improvement can be seen in following code:
>
> 7a6c: 48 0f a3 11 bt %rdx,(%rcx)
> 7a70: 19 d2 sbb %edx,%edx
> 7a72: 85 d2 test %edx,%edx
> 7a74: 74 eb je 7a61
>
> which becomes:
>
> 7a8c: 48 0f a3 11 bt %rdx,(%rcx)
> 7a90: 73 ef jae 7a81
>
> Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
> ---
> arch/x86/include/asm/bitops.h | 26 ++++++++++++++++++++++++--
> arch/x86/include/asm/percpu.h | 18 +++++++++++++++++-
> arch/x86/include/asm/signal.h | 6 ++++++
> arch/x86/include/asm/sync_bitops.h | 18 ++++++++++++++++++
> 4 files changed, 65 insertions(+), 3 deletions(-)
Nothing in your patch seems to be setting __GCC_ASM_FLAG_OUTPUTS__, and the patch
does not seem to be mailed as part of a larger series ...
So how is this supposed to work?
Thanks,
Ingo
next prev parent reply other threads:[~2015-07-27 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 0:07 [PATCH] x86: Introduce ASM flags to bitops Uros Bizjak
2015-07-27 15:40 ` Ingo Molnar [this message]
2015-07-27 15:50 ` Uros Bizjak
2015-07-27 15:54 ` Ingo Molnar
2015-07-27 15:59 ` Uros Bizjak
2015-07-27 16:13 ` Ingo Molnar
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=20150727154035.GA18213@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.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