Question on -fopt-info-inline

[Richard Biener]

On July 10, 2018 5:42:40 PM GMT+02:00, Qing Zhao <qing.zhao@oracle.com> wrote:
>Hi, David,
>
>thanks a lot for your information. very helpful.
>
>specifically, I am mostly interested in the inline report part of the
>opt-info:
>
>1. what’s the current status of inlining report through opt-info? 
>(with the upstream GCC last week,
>the -fopt-info-inline report nothing)
>2. what’s the plan for opt-info-inline? when will it be available?

Just implement it yourself? There is already Winline you can look at. 

>3. is there any design available for the messages from opt-info-inline?
>will the call-chain info, profiling 
>feedback info be available in the inlining report?

What do you need the report for? With C++ too much inlining happens to be interesting. You can also always look at the ipa-inline and einline dumps. 

Richard. 

>
>thanks.
>
>Qing
>
>> On Jul 5, 2018, at 3:55 PM, David Malcolm <dmalcolm@redhat.com>
>wrote:
>>>> 
>>>> where can I find more details of David’s work?
>>> 
>>> I don't have pointers to all the discussion handy.  BUt here's one
>of
>>> the early messages:
>>> 
>>> https://gcc.gnu.org/ml/gcc-patches/2018-05/msg01675.html
>> 
>> I'm currently attacking the problem of "better optimization
>> information" from two directions:
>> 
>> (a) More destinations for the existing optimization reports: being
>able
>> to send them through the diagnostics subsystem, and to be able to
>save
>> them in a machine-readable format from which reports can be generated
>> (e.g. prioritized by code hotness). The initial patch kit Jeff linked
>> to above introduced a new API for doing that, but I'm no longer doing
>> that, instead working on using the existing "dump_*" API in
>dumpfile.h.
>> Some of this work is now in trunk: dump messages are now tagged with
>> metadata about the hotness of the code being optimized, and where in
>> GCC's own code the messages was emitted from ...but this new metadata
>> is being dropped on the floor in dumpfile.c right now.  The latest
>> version of the patch kit for (a) is awaiting review at:
>>  "[PATCH 0/2] v4: optinfo framework and remarks"
>>     https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00066.html
><https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00066.html>
>> 
>> (b) I'm looking at new, improved optimization reports for
>> vectorization, by capturing higher-level information about why a loop
>> can't be vectorized, in a form that hopefully is useful to an
>end-user. 
>> See a (very rough) prototype here:
>> 
>>  * "[PATCH] [RFC] Higher-level reporting of vectorization problems"
>>    * https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01462.html
><https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01462.html>
>> 
>> I'm working on a less rough version of (b) and hope to post it to
>gcc-
>> patches soon.
>> 
>> Hope this sounds sane
>> Dave