From: Finn Thain <fthain@linux-m68k.org>
To: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Yury Norov <yury.norov@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Douglas Anderson <dianders@chromium.org>,
Kees Cook <keescook@chromium.org>,
Petr Mladek <pmladek@suse.com>,
Randy Dunlap <rdunlap@infradead.org>,
Zhaoyang Huang <zhaoyang.huang@unisoc.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Marco Elver <elver@google.com>, Brian Cain <bcain@quicinc.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Matthew Wilcox <willy@infradead.org>,
"Paul E . McKenney" <paulmck@kernel.org>,
linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH v4 2/5] m68k/bitops: use __builtin_{clz,ctzl,ffs} to evaluate constant expressions
Date: Sun, 28 Jan 2024 16:39:18 +1100 (AEDT) [thread overview]
Message-ID: <c47fedaf-cdc9-f970-460f-d2ee7e806da4@linux-m68k.org> (raw)
In-Reply-To: <20240128050449.1332798-3-mailhol.vincent@wanadoo.fr>
On Sun, 28 Jan 2024, Vincent Mailhol wrote:
> The compiler is not able to do constant folding on "asm volatile" code.
>
> Evaluate whether or not the function argument is a constant expression
> and if this is the case, return an equivalent builtin expression.
>
> On linux 6.7 with an allyesconfig and GCC 13.2.1, it saves roughly 11 KB.
>
> $ size --format=GNU vmlinux.before vmlinux.after
> text data bss total filename
> 60457964 70953697 2288644 133700305 vmlinux.before
> 60441196 70957057 2290724 133688977 vmlinux.after
>
> Reference: commit fdb6649ab7c1 ("x86/asm/bitops: Use __builtin_ctzl() to evaluate constant expressions")
> Link: https://git.kernel.org/torvalds/c/fdb6649ab7c1
>
> Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Signed-off-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
> ---
> arch/m68k/include/asm/bitops.h | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/arch/m68k/include/asm/bitops.h b/arch/m68k/include/asm/bitops.h
> index a8b23f897f24..02ec8a193b96 100644
> --- a/arch/m68k/include/asm/bitops.h
> +++ b/arch/m68k/include/asm/bitops.h
> @@ -469,6 +469,9 @@ static __always_inline unsigned long ffz(unsigned long word)
> {
> int res;
>
> + if (__builtin_constant_p(word))
> + return __builtin_ctzl(~word);
> +
> __asm__ __volatile__ ("bfffo %1{#0,#0},%0"
> : "=d" (res) : "d" (~word & -~word));
> return res ^ 31;
If the builtin has the desired behaviour, why do we reimplement it in asm?
Shouldn't we abandon one or the other to avoid having to prove (and
maintain) their equivalence?
> @@ -490,6 +493,9 @@ static __always_inline unsigned long ffz(unsigned long word)
> !defined(CONFIG_M68000)
> static __always_inline unsigned long __ffs(unsigned long x)
> {
> + if (__builtin_constant_p(x))
> + return __builtin_ctzl(x);
> +
> __asm__ __volatile__ ("bitrev %0; ff1 %0"
> : "=d" (x)
> : "0" (x));
> @@ -522,6 +528,9 @@ static __always_inline int ffs(int x)
> {
> int cnt;
>
> + if (__builtin_constant_p(x))
> + return __builtin_ffs(x);
> +
> __asm__ ("bfffo %1{#0:#0},%0"
> : "=d" (cnt)
> : "dm" (x & -x));
> @@ -540,6 +549,9 @@ static __always_inline int fls(unsigned int x)
> {
> int cnt;
>
> + if (__builtin_constant_p(x))
> + return x ? BITS_PER_TYPE(x) - __builtin_clz(x) : 0;
> +
> __asm__ ("bfffo %1{#0,#0},%0"
> : "=d" (cnt)
> : "dm" (x));
>
next prev parent reply other threads:[~2024-01-28 5:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221111081316.30373-1-mailhol.vincent@wanadoo.fr>
[not found] ` <20231217071250.892867-1-mailhol.vincent@wanadoo.fr>
[not found] ` <20231217071250.892867-2-mailhol.vincent@wanadoo.fr>
2024-01-02 10:28 ` [PATCH v3 1/5] m68k/bitops: force inlining of all bitops functions Geert Uytterhoeven
2024-01-07 12:01 ` Vincent MAILHOL
[not found] ` <20231217071250.892867-3-mailhol.vincent@wanadoo.fr>
2024-01-02 10:49 ` [PATCH v3 2/5] m68k/bitops: use __builtin_{clz,ctzl,ffs} to evaluate constant expressions Geert Uytterhoeven
2024-01-28 5:00 ` [PATCH v4 0/5] bitops: optimize code and add tests Vincent Mailhol
2024-01-28 5:00 ` [PATCH v4 1/5] m68k/bitops: force inlining of all bit-find functions Vincent Mailhol
2024-01-28 5:00 ` [PATCH v4 2/5] m68k/bitops: use __builtin_{clz,ctzl,ffs} to evaluate constant expressions Vincent Mailhol
2024-01-28 5:39 ` Finn Thain [this message]
2024-01-28 6:26 ` Vincent MAILHOL
2024-01-28 12:16 ` David Laight
2024-01-28 13:27 ` Vincent MAILHOL
2024-01-28 19:01 ` David Laight
2024-01-28 22:34 ` Finn Thain
2024-02-04 13:56 ` Vincent MAILHOL
2024-02-04 23:13 ` Finn Thain
2024-02-05 9:17 ` Vincent MAILHOL
2024-02-05 9:48 ` Finn Thain
2024-02-05 10:43 ` Vincent MAILHOL
2024-02-05 15:40 ` [PATCH] m68k/bitops: always use compiler's builtin for bit finding functions Vincent Mailhol
2024-02-07 6:31 ` [PATCH v4 2/5] m68k/bitops: use __builtin_{clz,ctzl,ffs} to evaluate constant expressions Finn Thain
2024-01-28 5:00 ` [PATCH v4 3/5] hexagon/bitops: force inlining of all bit-find functions Vincent Mailhol
2024-01-28 5:00 ` [PATCH v4 4/5] hexagon/bitops: use __builtin_{clz,ctzl,ffs} to evaluate constant expressions Vincent Mailhol
2024-01-28 5:00 ` [PATCH v4 5/5] lib: test_bitops: add compile-time optimization/evaluations assertions Vincent Mailhol
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=c47fedaf-cdc9-f970-460f-d2ee7e806da4@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=bcain@quicinc.com \
--cc=dianders@chromium.org \
--cc=elver@google.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=ndesaulniers@google.com \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=willy@infradead.org \
--cc=yury.norov@gmail.com \
--cc=zhaoyang.huang@unisoc.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