public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Aldy Hernandez <aldyh@redhat.com>,
	Jakub Jelinek <jakub@redhat.com>,
	Richard Biener <richard.guenther@gmail.com>,
	"MacLeod, Andrew" <amacleod@redhat.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Remove legacy VRP (maybe?)
Date: Mon, 21 Nov 2022 09:49:44 -0700	[thread overview]
Message-ID: <2eb36356-ffbf-6c8b-2824-08e204280d52@gmail.com> (raw)
In-Reply-To: <CAGm3qMWq0RZKyuQQ4uQ8eT2abg=N0MQEpoQ1TvSiZUz+kvEb-A@mail.gmail.com>


On 11/21/22 09:35, Aldy Hernandez via Gcc-patches wrote:
> I've been playing around with removing the legacy VRP code for the
> next release.  It's a layered onion to get this right, but the first
> bit is pretty straightforward and may be useful for this release.
> Basically, it entails removing the old VRP pass itself, along with
> value_range_equiv which have no producers left.  The current users of
> value_range_equiv don't put anything in the equivalence bitmaps, so
> they're basically behaving like plain value_range.
>
> I removed as much as possible without having to change any behavior,
> and this is what I came up with.  Is this something that would be
> useful for this release?  Would it help release managers have less
> unused cruft in the tree?
>
> Neither Andrew nor I have any strong feelings here.  We don't foresee
> the legacy code changing at all in the offseason, so we can just
> accumulate these patches in local trees.

I'd lean towards removal after gcc-13 releases.


jeff


  reply	other threads:[~2022-11-21 16:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21 16:35 Aldy Hernandez
2022-11-21 16:49 ` Jeff Law [this message]
2022-11-22  8:24   ` Richard Biener
2022-11-22  8:25     ` Richard Biener
2022-11-22  9:04       ` Aldy Hernandez
2022-11-22  9:22         ` Richard Biener
2022-11-22 13:40           ` Aldy Hernandez
2022-11-23 11:16             ` Aldy Hernandez
2022-11-23 20:09             ` Richard Biener

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=2eb36356-ffbf-6c8b-2824-08e204280d52@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=aldyh@redhat.com \
    --cc=amacleod@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).