public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Andrew Pinski <pinskia@gmail.com>,
	Aldy Hernandez <aldyh@redhat.com>,
	Andrew MacLeod <amacleod@redhat.com>,
	GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Using ranger from cfgexpand
Date: Sun, 3 Sep 2023 08:03:39 +0200	[thread overview]
Message-ID: <632F9135-9763-42E0-84F1-CAFA8A475C81@gmail.com> (raw)
In-Reply-To: <508aee8b-3e6b-788d-eda3-27c5282f4306@gmail.com>



> Am 03.09.2023 um 03:23 schrieb Jeff Law via Gcc <gcc@gcc.gnu.org>:
> 
> 
> 
>> On 9/2/23 18:40, Andrew Pinski via Gcc wrote:
>> Hi,
>>   I was trying to use the ranger from inside of cfgexpand but since at
>> this point we have a mix of RTL and gimple basic blocks, things fall
>> over very fast.
>> First does it make sense to use the ranger from expand or should we
>> change the gimple IR in isel instead if we have a better way of doing
>> an expansion.
>> In this case we have MIN_EXPR<a, 1> where a has a range of [0,INF] and
>> I want to expand it as (a != 0) to get better code.
> I very much want to get to a point where we can use ranges during expansion, but we're probably going to be limited to global ranges since as you note, we're in a mixed IL state and ranger is probably going to be confused as hell.

I think we want to move towards doing all the clever bits of RTL expansion as a preparation on GIMPLE which is what we have ISEL for.

Richard 

> 
> Jeff

      reply	other threads:[~2023-09-03  6:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-03  0:40 Andrew Pinski
2023-09-03  1:21 ` Jeff Law
2023-09-03  6:03   ` Richard Biener [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=632F9135-9763-42E0-84F1-CAFA8A475C81@gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=aldyh@redhat.com \
    --cc=amacleod@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=pinskia@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).