From: Jeff Law <jeffreyalaw@gmail.com>
To: Aldy Hernandez <aldyh@redhat.com>, GCC patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] path solver: Minimize exported ranges to subsequent blocks.
Date: Wed, 1 Dec 2021 09:38:13 -0700 [thread overview]
Message-ID: <10dd7eda-840d-717e-b2e3-a78189e4eadd@gmail.com> (raw)
In-Reply-To: <CAGm3qMVQWtEig=8Y5wC=F=JR5QK0rFcN0qfN9LTFrPi_OK=1=A@mail.gmail.com>
On 12/1/2021 9:18 AM, Aldy Hernandez via Gcc-patches wrote:
> I'm going to hold off pushing this until I hear from the global
> maintainers and/or release managers.
>
> This patch fixes a pathological performance case, but it may also be
> handled by Andrew's fixes in this area. It's up to y'all to decide if
> it's something we want in this release. An alternative would be to
> keep track of any pathological issues going forward, and see if this
> fixes the issue. I'm going to be taking leave any day now :).
I'm leaving this to you and Andrew to decide. Y'all know this code
better than anyone.
And yes, I keep expecting you to disappear without notice :-)
Jeff
prev parent reply other threads:[~2021-12-01 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 8:32 Aldy Hernandez
2021-12-01 16:18 ` Aldy Hernandez
2021-12-01 16: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=10dd7eda-840d-717e-b2e3-a78189e4eadd@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=aldyh@redhat.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).