LTO and the inlining of functions only called once.

[Diego Novillo]

On Sat, Oct 10, 2009 at 11:17, Daniel Jacobowitz <drow@false.org> wrote:
> 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.

Agreed.  We've had some discussions on this and there's been some
efforts started (http://gcc.gnu.org/wiki/Pass%20Activity%20Log), but
nothing concrete so far.

We should evolve a generic reporting facility for passes to produce
human readable logs on what they did, what they couldn't do, reasons,
etc.


Diego.