From: Jan Hubicka <hubicka@ucw.cz>
To: Jan Hubicka <hubicka@ucw.cz>,
Richard Guenther <richard.guenther@gmail.com>,
Toon Moene <toon@moene.org>, Jan Hubicka <jh@suse.cz>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: LTO and the inlining of functions only called once.
Date: Sat, 10 Oct 2009 15:28:00 -0000 [thread overview]
Message-ID: <20091010152704.GP9046@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20091010151737.GA18743@caradoc.them.org>
> On Sat, Oct 10, 2009 at 02:31:25PM +0200, Jan Hubicka wrote:
> > My solution would be probably to pass -fdump-ipa-inline parameter to lto
> > compilation and read the log. It lists the inlining decisions and if
> > something is not inlined, you get dump of reason why.
>
> GCC's dumps are really aimed at compiler developers. I think we would
> benefit from more "what is the compiler doing to my code" options
> (producing "note:"); things like which functions were inlined, which
> loops unrolled. We do already have this for vectorization.
We already have -Winline that dumps same info for all functions marked
inline. I am not sure if warning about all functions would help too
much, but I might be C centric where if I wanted to get something
inlined, I would use inline keyword :)
Honza
>
> --
> Daniel Jacobowitz
> CodeSourcery
next prev parent reply other threads:[~2009-10-10 15:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 11:00 Toon Moene
2009-10-10 11:34 ` Richard Guenther
2009-10-10 11:47 ` Toon Moene
2009-10-10 11:50 ` Richard Guenther
2009-10-10 12:18 ` Richard Guenther
2009-10-10 12:31 ` Toon Moene
2009-10-10 14:25 ` Toon Moene
2009-10-10 15:10 ` Richard Guenther
2009-10-10 13:40 ` Jan Hubicka
2009-10-10 15:27 ` Daniel Jacobowitz
2009-10-10 15:28 ` Jan Hubicka [this message]
2009-10-11 13:30 ` Toon Moene
2009-10-10 15:33 ` Diego Novillo
2009-10-10 17:26 ` Joseph S. Myers
2009-10-14 20:07 ` Paolo Bonzini
2009-10-10 16:40 ` Jeff Law
2009-10-10 17:16 ` Richard Guenther
2009-10-13 1:05 ` Jeff Law
2009-10-13 1:29 ` Michael Matz
2009-10-13 6:39 ` Jeff Law
2009-10-13 12:05 ` Paul Brook
2009-10-13 13:30 ` Daniel Jacobowitz
2009-10-13 15:15 ` Jeff Law
2009-10-13 18:31 ` Adam Nemet
2009-10-13 18:43 ` Toon Moene
2009-10-14 10:05 ` Richard Guenther
2009-10-14 13:48 ` Toon Moene
2009-10-14 14:04 ` Toon Moene
2009-10-14 14:43 ` Jan Hubicka
2009-10-14 16:49 ` Daniel Jacobowitz
2009-10-14 18:20 ` Toon Moene
2009-10-14 18:58 ` Paolo Bonzini
2009-10-14 19:09 ` Paolo Bonzini
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=20091010152704.GP9046@atrey.karlin.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=richard.guenther@gmail.com \
--cc=toon@moene.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).