From: Jason Merrill <jason@redhat.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>,
"MacLeod, Andrew" <amacleod@redhat.com>
Subject: Re: 1.76% performance loss in VRP due to inlining
Date: Tue, 30 Apr 2024 15:09:51 -0400 [thread overview]
Message-ID: <CADzB+2=ptBaKFMj3zJgh-UM9Zuh0B8_RRmfVZhBESRFhkGQspA@mail.gmail.com> (raw)
In-Reply-To: <CAGm3qMVXdshX8T+ioAmEf2=5D8tzCHtZrmhzs0xcSTdUo0qCFg@mail.gmail.com>
On Fri, Apr 26, 2024 at 5:44 AM Aldy Hernandez via Gcc <gcc@gcc.gnu.org> wrote:
>
> In implementing prange (pointer ranges), I have found a 1.74% slowdown
> in VRP, even without any code path actually using the code. I have
> tracked this down to irange::get_bitmask() being compiled differently
> with and without the bare bones patch. With the patch,
> irange::get_bitmask() has a lot of code inlined into it, particularly
> get_bitmask_from_range() and consequently the wide_int_storage code.
...
> +static irange_bitmask
> +get_bitmask_from_range (tree type,
> + const wide_int &min, const wide_int &max)
...
> -irange_bitmask
> -irange::get_bitmask_from_range () const
My guess is that this is the relevant change: the old function has
external linkage, and is therefore interposable, which inhibits
inlining. The new function has internal linkage, which allows
inlining.
Relatedly, I wonder if we want to build GCC with -fno-semantic-interposition?
Jason
next prev parent reply other threads:[~2024-04-30 19:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 9:42 Aldy Hernandez
2024-04-30 7:57 ` Richard Biener
2024-04-30 8:21 ` Aldy Hernandez
2024-04-30 8:53 ` Martin Jambor
2024-04-30 19:09 ` Jason Merrill [this message]
2024-04-30 19:15 ` Richard Biener
2024-04-30 21:48 ` Building libgccjit with -fno-semantic-interposition? ( was Re: 1.76% performance loss in VRP due to inlining) David Malcolm
2024-05-02 7:40 ` Andrea Corallo
2024-04-30 19:22 ` 1.76% performance loss in VRP due to inlining Jakub Jelinek
2024-04-30 21:37 ` Jason Merrill
2024-05-03 8:55 ` Aldy Hernandez
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='CADzB+2=ptBaKFMj3zJgh-UM9Zuh0B8_RRmfVZhBESRFhkGQspA@mail.gmail.com' \
--to=jason@redhat.com \
--cc=aldyh@redhat.com \
--cc=amacleod@redhat.com \
--cc=gcc@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).