public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Philipp Tomsich <philipp.tomsich@vrull.eu>, gcc-patches@gcc.gnu.org
Cc: Kito Cheng <kito.cheng@gmail.com>,
	Vineet Gupta <vineetg@rivosinc.com>,
	Palmer Dabbelt <palmer@rivosinc.com>,
	Christoph Muellner <christoph.muellner@vrull.eu>,
	Jeff Law <jlaw@ventanamicro.com>
Subject: Re: [PATCH] RISC-V: split to allow formation of sh[123]add before divw
Date: Fri, 18 Nov 2022 12:37:45 -0700	[thread overview]
Message-ID: <a3d1e1d9-0965-5338-26da-274c01c3d1b0@gmail.com> (raw)
In-Reply-To: <20221108195617.2701379-1-philipp.tomsich@vrull.eu>


On 11/8/22 12:56, Philipp Tomsich wrote:
> When using strength-reduction, we will reduce a multiplication to a
> sequence of shifts and adds.  If this is performed with 32-bit types
> and followed by a division, the lack of w-form sh[123]add will make
> combination impossible and lead to a slli + addw being generated.
>
> Split the sequence with the knowledge that a w-form div will perform
> implicit sign-extensions.
>
> gcc/ChangeLog:
>
>          * config/riscv/bitmanip.md: Add a define_split to optimize
>            slliw + addiw + divw into sh[123]add + divw.
>
> gcc/testsuite/ChangeLog:
>
>          * gcc.target/riscv/zba-shNadd-05.c: New test.

OK.  I won't complain about the subregs on this one :-)


jeff



  reply	other threads:[~2022-11-18 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 19:56 Philipp Tomsich
2022-11-18 19:37 ` Jeff Law [this message]
2022-11-18 19:56   ` Philipp Tomsich

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=a3d1e1d9-0965-5338-26da-274c01c3d1b0@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=christoph.muellner@vrull.eu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jlaw@ventanamicro.com \
    --cc=kito.cheng@gmail.com \
    --cc=palmer@rivosinc.com \
    --cc=philipp.tomsich@vrull.eu \
    --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).