From: Jeff Law <jeffreyalaw@gmail.com>
To: Richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Cc: Jakub Jelinek <jakub@redhat.com>, Michael Matz <matz@suse.de>
Subject: Re: [PATCH] middle-end/114579 - speed up add_scope_conflicts
Date: Fri, 5 Apr 2024 09:09:24 -0600 [thread overview]
Message-ID: <46b18cf0-cc20-4fb2-a347-89d3f9f13b37@gmail.com> (raw)
In-Reply-To: <20240404124128.752263858C78@sourceware.org>
On 4/4/24 6:41 AM, Richard Biener wrote:
> The following speeds up stack variable conflict detection by recognizing
> that the all-to-all conflict recording is only necessary for CFG merges
> as it's the unioning of the live variable sets that doesn't come with
> explicit mentions we record conflicts for.
>
> If we employ this optimization we have to make sure to perform the
> all-to-all conflict recording for all CFG merges even those into
> empty blocks where we might previously have skipped this.
>
> I have reworded the comment before the all-to-all conflict recording
> since it seemed to be confusing and missing the point - but maybe I
> am also missing something here.
>
> Nevertheless for the testcase in the PR the compile-time spend in
> add_scope_conflicts at -O1 drops from previously 67s (39%) to 10s (9%).
>
> Bootstrapped and tested on x86_64-unknown-linux-gnu, OK for trunk?
>
> Thanks,
> Richard.
>
> PR middle-end/114579
> * cfgexpand.cc (add_scope_conflicts_1): Record all-to-all
> conflicts only when there's a CFG merge but for all CFG merges.
OK. Your call on whether or not to include in gcc-14 or wait for gcc-15.
jeff
next parent reply other threads:[~2024-04-05 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240404124128.752263858C78@sourceware.org>
2024-04-05 15:09 ` Jeff Law [this message]
2024-04-04 13:32 Michael Matz
-- strict thread matches above, loose matches on Subject: below --
2024-04-04 12:41 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=46b18cf0-cc20-4fb2-a347-89d3f9f13b37@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=matz@suse.de \
--cc=rguenther@suse.de \
/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).