From: Navid Rahimi <navidrahimi@microsoft.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>,
Edgar Mobile <heideggm@hotmail.com>
Subject: Re: Try to understand output of -fdump-ipa-inline
Date: Tue, 19 Jul 2022 18:27:56 +0000 [thread overview]
Message-ID: <CY4PR21MB15408E1E2EA71599B6531256A38F9@CY4PR21MB1540.namprd21.prod.outlook.com> (raw)
In-Reply-To: <DM8PR16MB4357F46E64E303437796FF53C78F9@DM8PR16MB4357.namprd16.prod.outlook.com>
Have you tried to make a similar example? What I do in this situation is try to replicate exact situation but in a smaller case.
Inlining decision happens in multiple levels. It is hard to find out what is the exact reason this way.
Just as experiment, try it with always_inline [1] too.
1. https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html
Best wishes,
Navid.
________________________________________
From: Gcc-help <gcc-help-bounces+navidrahimi=microsoft.com@gcc.gnu.org> on behalf of Edgar Mobile via Gcc-help <gcc-help@gcc.gnu.org>
Sent: Tuesday, July 19, 2022 06:56
To: gcc-help@gcc.gnu.org
Subject: [EXTERNAL] Try to understand output of -fdump-ipa-inline
Greetings,
I try to find out why a function (inline keyword, defined in header) is not inlined. Example for -fdump-ipa-inline output:
Considering void Vertex::update(const Data&)/5927 with 40 size
to be inlined into void SomeClass::updatePoly(const Data&, Polyline&)/11181 in /somepath/SomeClass.cpp:663
Estimated badness is -0.000083, frequency 4.69.
The function is never inlined. unfortunately, the code is proprietary, so I cannot post everything.
Can anyone explain me the message above to find out why?
Thanks
next prev parent reply other threads:[~2022-07-19 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 13:56 Edgar Mobile
2022-07-19 18:27 ` Navid Rahimi [this message]
2022-07-20 8:10 ` Edgar Mobile
2022-07-20 19:35 ` Navid Rahimi
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=CY4PR21MB15408E1E2EA71599B6531256A38F9@CY4PR21MB1540.namprd21.prod.outlook.com \
--to=navidrahimi@microsoft.com \
--cc=gcc-help@gcc.gnu.org \
--cc=heideggm@hotmail.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).