From: Oleg Endo <oleg.endo@t-online.de>
To: Jeff Law <jlaw@ventanamicro.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Jivan Hakobyan <jivanhakobyan9@gmail.com>
Subject: Re: [RFA] New pass for sign/zero extension elimination
Date: Mon, 20 Nov 2023 11:57:28 +0900 [thread overview]
Message-ID: <4e12744d14456a538fe34b80a758c5462d788d06.camel@t-online.de> (raw)
In-Reply-To: <463a5426-ad0b-4b2f-b630-2b7e664c65bb@ventanamicro.com>
On Sun, 2023-11-19 at 19:51 -0700, Jeff Law wrote:
>
> On 11/19/23 18:22, Oleg Endo wrote:
> >
> > On Sun, 2023-11-19 at 17:47 -0700, Jeff Law wrote:
> > > This is work originally started by Joern @ Embecosm.
> > >
> > > There's been a long standing sense that we're generating too many
> > > sign/zero extensions on the RISC-V port. REE is useful, but it's really
> > > focused on a relatively narrow part of the extension problem.
> > >
> > > What Joern's patch does is introduce a new pass which tracks liveness of
> > > chunks of pseudo regs. Specifically it tracks bits 0..7, 8..15, 16..31
> > > and 32..63.
> > >
> > > If it encounters a sign/zero extend that sets bits that are never read,
> > > then it replaces the sign/zero extension with a narrowing subreg. The
> > > narrowing subreg usually gets eliminated by subsequent passes (it's just
> > > a copy after all).
> > >
> >
> > Have you tried it on SH, too? (and if so any numbers?)
> Just bootstrap with C regression testing on sh4/sh4eb. No data on
> improvements.
>
Alright. I'll check what it does for SH once it's in.
Cheers,
Oleg
next prev parent reply other threads:[~2023-11-20 2:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 0:47 Jeff Law
2023-11-20 1:22 ` Oleg Endo
2023-11-20 2:51 ` Jeff Law
2023-11-20 2:57 ` Oleg Endo [this message]
2023-11-20 2:23 ` Xi Ruoyao
2023-11-20 2:46 ` Jeff Law
2023-11-20 2:52 ` Jeff Law
2023-11-20 3:32 ` Xi Ruoyao
2023-11-20 3:48 ` Jeff Law
2023-11-20 18:26 ` Richard Sandiford
2023-11-22 17:59 ` Jeff Law
2023-11-27 20:15 ` Richard Sandiford
2023-11-20 18:56 ` Dimitar Dimitrov
2023-11-22 22:23 ` Jeff Law
2023-11-26 16:42 ` rep.dot.nop
2023-11-27 16:14 ` Jeff Law
2023-11-27 11:30 ` Andrew Stubbs
2023-11-27 16:16 ` Jeff Law
2023-12-01 1:08 ` Hans-Peter Nilsson
2023-12-01 15:09 ` Jeff Law
2023-12-01 16:17 ` Hans-Peter Nilsson
2023-11-27 17:36 Joern Rennecke
2023-11-27 17:57 ` Joern Rennecke
2023-11-27 20:03 ` Richard Sandiford
2023-11-27 20:18 ` Jeff Law
2023-11-28 13:36 ` Joern Rennecke
2023-11-28 14:09 ` Joern Rennecke
2023-11-30 17:33 ` Jeff Law
2023-11-28 13:13 ` Joern Rennecke
2023-11-28 5:50 ` Jeff Law
2023-11-27 18:19 Joern Rennecke
2023-11-28 5:51 ` Jeff Law
2023-11-29 17:37 Joern Rennecke
2023-11-29 19:13 ` Jivan Hakobyan
2023-11-30 15:37 ` Jeff Law
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=4e12744d14456a538fe34b80a758c5462d788d06.camel@t-online.de \
--to=oleg.endo@t-online.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jivanhakobyan9@gmail.com \
--cc=jlaw@ventanamicro.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).