From: Philipp Tomsich <philipp.tomsich@vrull.eu>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Palmer Dabbelt <palmer@rivosinc.com>,
Vineet Gupta <vineetg@rivosinc.com>,
Jeff Law <jlaw@ventanamicro.com>,
Christoph Muellner <christoph.muellner@vrull.eu>,
Kito Cheng <kito.cheng@gmail.com>
Subject: Re: [PATCH v2] RISC-V: costs: support shift-and-add in strength-reduction
Date: Sun, 13 Nov 2022 16:40:46 +0100 [thread overview]
Message-ID: <CAAeLtUBEw-=K48ZTOwtHzYY2xD-+Evw-8p2p_1ju_dZJx5P2bQ@mail.gmail.com> (raw)
In-Reply-To: <1feb8f91-cacc-dacf-afd9-098c3ab59b4b@gmail.com>
Applied to master. Thanks!
Note that the multiply-by-200 (in the testcase) originates from Dhrystone.
Philipp.
On Sun, 13 Nov 2022 at 02:23, Jeff Law <jeffreyalaw@gmail.com> wrote:
>
>
> On 11/10/22 14:34, Philipp Tomsich wrote:
> > The strength-reduction implementation in expmed.cc will assess the
> > profitability of using shift-and-add using a RTL expression that wraps
> > a MULT (with a power-of-2) in a PLUS. Unless the RISC-V rtx_costs
> > function recognizes this as expressing a sh[123]add instruction, we
> > will return an inflated cost---thus defeating the optimization.
> >
> > This change adds the necessary idiom recognition to provide an
> > accurate cost for this for of expressing sh[123]add.
> >
> > Instead on expanding to
> > li a5,200
> > mulw a0,a5,a0
> > with this change, the expression 'a * 200' is sythesized as:
> > sh2add a0,a0,a0 // *5 = a + 4 * a
> > sh2add a0,a0,a0 // *5 = a + 4 * a
> > slli a0,a0,3 // *8
> >
> > gcc/ChangeLog:
> >
> > * config/riscv/riscv.c (riscv_rtx_costs): Recognize shNadd,
> > if expressed as a plus and multiplication with a power-of-2.
> > Split costing for MINUS from PLUS.
> >
> > gcc/testsuite/ChangeLog:
> >
> > * gcc.target/riscv/zba-shNadd-07.c: New test.
>
> OK. Note that getting this right can impact one of the spec2017 integer
> benchmarks notably. I don't recall which one, but it has a div and a
> mod by the same constant which is fairly reasonably implement with
> shifts and adds. You won't see it in instruction count data, but would
> see it if you had cycle count data or instrumented for div/mod instructions.
>
>
> Jeff
>
>
prev parent reply other threads:[~2022-11-13 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 21:34 Philipp Tomsich
2022-11-13 1:23 ` Jeff Law
2022-11-13 15:40 ` Philipp Tomsich [this message]
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='CAAeLtUBEw-=K48ZTOwtHzYY2xD-+Evw-8p2p_1ju_dZJx5P2bQ@mail.gmail.com' \
--to=philipp.tomsich@vrull.eu \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=jlaw@ventanamicro.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).