From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Remove legacy EVRP code.
Date: Tue, 28 Jun 2022 07:38:55 -0600 [thread overview]
Message-ID: <0f667a33-bf0f-3c4c-b087-05bebb2f9138@gmail.com> (raw)
In-Reply-To: <CAFiYyc3Hr7J6UFXTDk95t+DzZFMw_6vUuTBKXeQd60DorDW_mQ@mail.gmail.com>
On 6/28/2022 1:37 AM, Richard Biener via Gcc-patches wrote:
> On Mon, Jun 27, 2022 at 9:04 PM Aldy Hernandez <aldyh@redhat.com> wrote:
>> With DOM converted to ranger, there are no longer any uses of the EVRP
>> engine. For that matter, we haven't used the legacy mode in quite a
>> while, so I think it's safe to remove any associated code.
>>
>> There are some methods in vr_values which should now be private, but I
>> didn't bother changing them, as most of the vr_values class will be
>> removed when VRP1 is converted to ranger.
>>
>> Does anyone have any issues with me pushing this?
> Fine with me.
Likewise.
jeff
prev parent reply other threads:[~2022-06-28 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 19:03 Aldy Hernandez
2022-06-28 7:37 ` Richard Biener
2022-06-28 12:45 ` Aldy Hernandez
2022-06-28 13:38 ` Jeff Law [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=0f667a33-bf0f-3c4c-b087-05bebb2f9138@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/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).