public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Hans-Peter Nilsson <hp@axis.com>, Jeff Law <jlaw@ventanamicro.com>
Cc: gcc-patches@gcc.gnu.org, jivanhakobyan9@gmail.com
Subject: Re: [RFA] New pass for sign/zero extension elimination
Date: Fri, 1 Dec 2023 08:09:08 -0700	[thread overview]
Message-ID: <b691064f-7dec-4c0d-9ca4-bdf8022eebce@gmail.com> (raw)
In-Reply-To: <20231201010817.0B1FF20431@pchp3.se.axis.com>



On 11/30/23 18:08, Hans-Peter Nilsson wrote:
>> Date: Sun, 19 Nov 2023 17:47:56 -0700
>> From: Jeff Law <jlaw@ventanamicro.com>
> 
>> Locally we have had this enabled at -O1 and above to encourage testing,
>> but I'm thinking that for the trunk enabling at -O2 and above is the
>> right thing to do.
> 
> Yes.
> 
>> Thoughts, comments, recommendations?
> 
> Sounds great!
> 
> It'd be nice if its framework can be re-used for
> target-specific passes, doing quirky sign- or zero-extend-
> related optimizations (those that are not just sign- or
> zero-extend removal).  Perhaps most of those opportunities
> can be implemented as target hooks in this pass.  Definitely
> not asking for a change, just imagining future improvements.
> 
> Also, I haven't followed the thread and its branches, just
> offering a word encouragement.
What kind of quirky target things did you have in mind?  If there's 
overlap with things we need I might be able to find someone to take it 
on.  Or might be able to suggest how they can be handled.


jeff

  reply	other threads:[~2023-12-01 15:09 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
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 [this message]
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=b691064f-7dec-4c0d-9ca4-bdf8022eebce@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hp@axis.com \
    --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).