From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Sunil K Pandey <skpgkp2@gmail.com>, libc-alpha@sourceware.org
Cc: hjl.tools@gmail.com
Subject: Re: [PATCH v2] x86_64: Optimize ffsll function code size.
Date: Mon, 31 Jul 2023 17:12:23 -0300 [thread overview]
Message-ID: <587651e8-c4e1-7d83-76fa-7395f68e457f@linaro.org> (raw)
In-Reply-To: <20230731183549.2396362-1-skpgkp2@gmail.com>
On 31/07/23 15:35, Sunil K Pandey via Libc-alpha wrote:
> Ffsll function size is 17 byte, this patch optimizes size to 16 byte.
> Currently ffsll function randomly regress by ~20%, depending on how
> code get aligned.
>
> This patch fixes ffsll function random performance regression.
>
> Changes from v1:
> - Further reduce size ffsll function size to 12 bytes.
> ---
> sysdeps/x86_64/ffsll.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/sysdeps/x86_64/ffsll.c b/sysdeps/x86_64/ffsll.c
> index a1c13d4906..6a5803c7c1 100644
> --- a/sysdeps/x86_64/ffsll.c
> +++ b/sysdeps/x86_64/ffsll.c
> @@ -26,13 +26,13 @@ int
> ffsll (long long int x)
> {
> long long int cnt;
> - long long int tmp;
>
> - asm ("bsfq %2,%0\n" /* Count low bits in X and store in %1. */
> - "cmoveq %1,%0\n" /* If number was zero, use -1 as result. */
> - : "=&r" (cnt), "=r" (tmp) : "rm" (x), "1" (-1));
> + asm ("mov $-1,%k0\n" /* Intialize CNT to -1. */
> + "bsf %1,%0\n" /* Count low bits in X and store in CNT. */
> + "inc %k0\n" /* Increment CNT by 1. */
> + : "=&r" (cnt) : "r" (x));
>
> - return cnt + 1;
> + return cnt;
> }
>
> #ifndef __ILP32__
I still prefer if we can just remove this arch-optimized function in favor
in compiler builtins.
next prev parent reply other threads:[~2023-07-31 20:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 16:05 [PATCH] " Sunil K Pandey
2023-07-26 16:38 ` Richard Henderson
2023-07-26 16:50 ` H.J. Lu
2023-07-26 16:51 ` Noah Goldstein
2023-07-26 16:51 ` Sunil Pandey
2023-07-26 16:59 ` Noah Goldstein
2023-07-26 17:11 ` Adhemerval Zanella Netto
2023-07-27 0:31 ` Cristian Rodríguez
2023-07-26 20:43 ` Sunil Pandey
2023-07-26 21:05 ` Noah Goldstein
2023-07-26 22:37 ` Sunil Pandey
2023-07-27 0:00 ` Noah Goldstein
2023-07-27 8:16 ` Florian Weimer
2023-07-27 11:46 ` Alexander Monakov
2023-07-27 12:10 ` Florian Weimer
2023-07-27 13:59 ` Cristian Rodríguez
2023-07-27 14:00 ` Alexander Monakov
2023-07-27 15:13 ` Sunil Pandey
2023-07-27 15:50 ` Alexander Monakov
2023-07-27 16:24 ` Florian Weimer
2023-07-27 16:35 ` Adhemerval Zanella Netto
2023-07-27 17:09 ` Florian Weimer
2023-07-27 17:25 ` Sunil Pandey
2023-07-31 18:35 ` [PATCH v2] " Sunil K Pandey
2023-07-31 20:12 ` Adhemerval Zanella Netto [this message]
2023-07-31 20:58 ` Sunil Pandey
2023-07-31 22:57 ` Adhemerval Zanella Netto
2023-07-31 23:44 ` Sunil Pandey
2023-07-31 23:54 ` Noah Goldstein
2023-08-01 6:47 ` Andreas Schwab
2023-08-01 13:46 ` Adhemerval Zanella Netto
2023-08-01 18:25 ` Cristian Rodríguez
2024-01-10 19:19 ` Carlos O'Donell
2024-01-25 3:10 ` Sunil Pandey
2023-07-27 16:40 ` [PATCH] " Sunil Pandey
2023-07-26 17:04 ` Noah Goldstein
2023-07-26 17:25 ` Andrew Pinski
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=587651e8-c4e1-7d83-76fa-7395f68e457f@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=skpgkp2@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).