From: Andrew MacLeod <amacleod@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"hernandez, aldy" <aldyh@redhat.com>
Subject: Re: [PATCH] [GCC13] PR tree-optimization/110315 - Add auto-resizing capability to irange's
Date: Mon, 24 Jul 2023 13:05:12 -0400 [thread overview]
Message-ID: <c6f38727-90ce-5f91-ed6b-597ef72512cb@redhat.com> (raw)
In-Reply-To: <0FE687D6-F12D-42EE-969F-952E347CD899@gmail.com>
On 7/24/23 12:49, Richard Biener wrote:
>
>> Am 24.07.2023 um 16:40 schrieb Andrew MacLeod via Gcc-patches <gcc-patches@gcc.gnu.org>:
>>
>> Aldy has ported his irange reduction patch to GCC 13. It resolves this PR.
>>
>> I have bootstrapped it and it passes regression tests.
>>
>> Do we want to check it into the GCC 13 branch? The patch has all his comments in it.
> Please wait until the branch is open again, then yes , I think we want this there. Was there any work reducing the recursion depth that’s worth backporting as well?
>
>
I think most of the recursion depth work is in GCC13. Im looking at a
few more tweaks for GCC14, but they are fairly minor at the moment.
reduction of the size of the stack was the huge win.
prev parent reply other threads:[~2023-07-24 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 14:39 Andrew MacLeod
2023-07-24 16:49 ` Richard Biener
2023-07-24 17:05 ` Andrew MacLeod [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=c6f38727-90ce-5f91-ed6b-597ef72512cb@redhat.com \
--to=amacleod@redhat.com \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--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).