From: Aldy Hernandez <aldyh@redhat.com>
To: Martin Jambor <mjambor@suse.cz>, GCC patches <gcc-patches@gcc.gnu.org>
Cc: Andrew MacLeod <amacleod@redhat.com>
Subject: Re: [PATCH] Implement ipa_vr hashing.
Date: Wed, 7 Jun 2023 12:01:18 +0200 [thread overview]
Message-ID: <030045cc-fa24-0b6f-f5bf-6f626a753376@redhat.com> (raw)
In-Reply-To: <ri6r0qz9onv.fsf@suse.cz>
On 5/29/23 16:51, Martin Jambor wrote:
> Hi,
>
> On Mon, May 22 2023, Aldy Hernandez via Gcc-patches wrote:
>> Implement hashing for ipa_vr. When all is said and done, all these
>> patches incurr a 7.64% slowdown for ipa-cp, with is entirely covered by
>> the similar 7% increase in this area last week. So we get type agnostic
>> ranges with "infinite" range precision close to free.
>
> Do you know why/where this slow-down happens? Do we perhaps want to
> limit the "infiniteness" a little somehow?
It happens in ipcp_vr_lattice::meet_with_1, because we have a lot more
sub-ranges to union. The latest numbers are 6.6%, and as I said I've
already improved ipa-cp by the an equal amount, so we're good :).
The infiniteness is already capped. We start at 3 sub-ranges, and grow
up to 255. I suppose if this is a problem, we could write a custom
Value_Range temporary for IPA to fit specific needs, but I'd really like
to avoid such special casing.
>
> Also, jump functions live for a long time, have you looked at how memory
> hungry they become? I hope that the hashing would be good at preventing
> any issues.
See my previous mail on memory usage.
Aldy
next prev parent reply other threads:[~2023-06-07 10:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 18:56 [PATCH] Convert ipa_jump_func to use ipa_vr instead of a value_range Aldy Hernandez
2023-05-22 18:56 ` [PATCH] Implement ipa_vr hashing Aldy Hernandez
2023-05-29 14:51 ` Martin Jambor
2023-06-07 10:01 ` Aldy Hernandez [this message]
2023-06-10 20:30 ` Aldy Hernandez
2023-06-14 12:11 ` Aldy Hernandez
2023-06-22 5:49 ` Aldy Hernandez
2023-06-26 9:22 ` Aldy Hernandez
2023-06-26 9:23 ` Aldy Hernandez
2023-06-26 16:40 ` Martin Jambor
2023-05-22 18:56 ` [PATCH] Convert remaining uses of value_range in ipa-*.cc to Value_Range Aldy Hernandez
2023-06-14 12:10 ` Aldy Hernandez
2023-06-22 5:49 ` Aldy Hernandez
2023-06-26 16:41 ` Martin Jambor
2023-06-14 12:09 ` [PATCH] Convert ipa_jump_func to use ipa_vr instead of a value_range Aldy Hernandez
2023-06-22 5:49 ` Aldy Hernandez
2023-06-26 16:40 ` Martin Jambor
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=030045cc-fa24-0b6f-f5bf-6f626a753376@redhat.com \
--to=aldyh@redhat.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mjambor@suse.cz \
/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).