From: Philipp Tomsich <philipp.tomsich@vrull.eu>
To: Vineet Gupta <vineetg@rivosinc.com>
Cc: gcc-patches@gcc.gnu.org, kito.cheng@gmail.com,
Palmer Dabbelt <palmer@rivosinc.com>,
Christoph Mullner <christoph.muellner@vrull.eu>,
Jeff Law <jeffreyalaw@gmail.com>,
gnu-toolchain@rivosinc.com
Subject: Re: [PATCH] RISC-V: costs: miscomputed shiftadd_cost triggering synth_mult [PR/108987]
Date: Wed, 1 Mar 2023 20:56:22 +0100 [thread overview]
Message-ID: <CAAeLtUCCb1qgAZfaZjgU9rNKDSRvy0NtkZ=Fv4h-=uoLTTm4Vw@mail.gmail.com> (raw)
In-Reply-To: <20230301195315.1793087-1-vineetg@rivosinc.com>
On Wed, 1 Mar 2023 at 20:53, Vineet Gupta <vineetg@rivosinc.com> wrote:
>
> This showed up as dynamic icount regression in SPEC 531.deepsjeng with upstream
> gcc (vs. gcc 12.2). gcc was resorting to synthetic multiply using shift+add(s)
> even when multiply had clear cost benefit.
>
> |00000000000133b8 <see(state_t*, int, int, int, int) [clone .constprop.0]+0x382>:
> | 133b8: srl a3,a1,s6
> | 133bc: and a3,a3,s5
> | 133c0: slli a4,a3,0x9
> | 133c4: add a4,a4,a3
> | 133c6: slli a4,a4,0x9
> | 133c8: add a4,a4,a3
> | 133ca: slli a3,a4,0x1b
> | 133ce: add a4,a4,a3
>
> vs. gcc 12 doing something lke below.
>
> |00000000000131c4 <see(state_t*, int, int, int, int) [clone .constprop.0]+0x35c>:
> | 131c4: ld s1,8(sp)
> | 131c6: srl a3,a1,s4
> | 131ca: and a3,a3,s11
> | 131ce: mul a3,a3,s1
>
> Bisected this to f90cb39235c4 ("RISC-V: costs: support shift-and-add in
> strength-reduction"). The intent was to optimize cost for
> shift-add-pow2-{1,2,3} corresponding to bitmanip insns SH*ADD, but ended
> up doing that for all shift values which seems to favor synthezing
> multiply among others.
>
> The bug itself is trivial, IN_RANGE() calling pow2p_hwi() which returns bool
> vs. exact_log2() returning power of 2.
>
> This fix also requires update to the test introduced by the same commit
> which now generates MUL vs. synthesizing it.
>
> gcc/Changelog:
>
> * config/riscv/riscv.cc (riscv_rtx_costs): Fixed IN_RANGE() to
> use exact_log2().
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/zba-shNadd-07.c: f2(i*783) now generates MUL vs.
> 5 insn sh1add+slli+add+slli+sub.
> * gcc.target/riscv/pr108987.c: New test.
>
> Signed-off-by: Vineet Gupta <vineetg@rivosinc.com>
Reviewed-by: Philipp Tomsich <philipp.tomsich@vrull.eu>
next prev parent reply other threads:[~2023-03-01 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 19:53 Vineet Gupta
2023-03-01 19:56 ` Philipp Tomsich [this message]
2023-03-23 8:42 ` Kito Cheng
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='CAAeLtUCCb1qgAZfaZjgU9rNKDSRvy0NtkZ=Fv4h-=uoLTTm4Vw@mail.gmail.com' \
--to=philipp.tomsich@vrull.eu \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@rivosinc.com \
--cc=vineetg@rivosinc.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).