public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jim Wilson <jimw@sifive.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
	Nidal Faour <Nidal.Faour@wdc.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Ofer Shinaar <Ofer.Shinaar@wdc.com>,
	Craig Blackmore <craig.blackmore@embecosm.com>
Subject: Re: Remove redundant zero extend
Date: Thu, 12 Mar 2020 19:54:10 -0500	[thread overview]
Message-ID: <20200313005410.GM22482@gate.crashing.org> (raw)
In-Reply-To: <CAFyWVabKX69aaws_qHj9GVTjAngx-DwONbSeWQBH=fb7ezVvYA@mail.gmail.com>

Hi!

On Thu, Mar 12, 2020 at 02:43:06PM -0700, Jim Wilson wrote:
> I looked at combine because I'm familiar with that pass, but the ree
> pass might be the right place to handle this.

IMO, part of this should perhaps be done on Gimple already.  But the part
that should be done on RTL should be done *early*, it should start before
the loop optimisations, and it should be *finished* before combine.

>  I don't know if it has
> any support for handling if statements.  If not, maybe it could be
> extended to handle cases like this.

No, combine cannot do anything that crosses basic blocks.


Segher

  reply	other threads:[~2020-03-13  0:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 13:04 Nidal Faour
2020-03-11 13:11 ` David Malcolm
2020-03-11 13:34   ` Nidal Faour
2020-11-16 22:47     ` Jeff Law
2020-03-12  3:05 ` Jeff Law
2020-03-12  9:38   ` Richard Biener
2020-03-12 21:43     ` Jim Wilson
2020-03-13  0:54       ` Segher Boessenkool [this message]
2020-03-13 21:29       ` 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=20200313005410.GM22482@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=Nidal.Faour@wdc.com \
    --cc=Ofer.Shinaar@wdc.com \
    --cc=craig.blackmore@embecosm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jimw@sifive.com \
    --cc=richard.guenther@gmail.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).