This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: LTO and the inlining of functions only called once.


On Sat, Oct 10, 2009 at 6:24 PM, Jeff Law <law@redhat.com> wrote:
> On 10/10/09 09:17, Daniel Jacobowitz 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.
>>
>
> Interestingly enough, some of the Red Hat folks were having this exact
> discussion re: inlining with a customer last week.
>
> What I was starting to think was to include both functions which were
> inlined, but also functions which were not inlined and the heuristic limits
> that caused the function not to be inlined.

Well - that will print one diagnostic per callgraph edge.  A bit too much, no?

Richard.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]