Displaying 4 results from an estimated 4 matches for "d19678".
2016 May 11
2
Filter optimization remarks by the hotness of the code region
...ave. I don't think that the backend should be responsible for filtering, but should pass the relative hotness information to the frontend. Given that these diagnostics are not just going to be used for -Rpass and friends, but also for generating reports by other tools (see the discussion around D19678, for example), I think it is important to allow the frontend to filter.
I am not sure I follow, can you please elaborate. Are you saying that for example in the listing use case we don’t want the filtered diagnostics? In other words it should be up to the remark handler to decide whether it want...
2016 May 11
4
Filter optimization remarks by the hotness of the code region
...sponsible for filtering, but should
>>> pass the relative hotness information to the frontend. Given that
>>> these diagnostics are not just going to be used for -Rpass and
>>> friends, but also for generating reports by other tools (see the
>>> discussion around D19678, for example), I think it is important to
>>> allow the frontend to filter.
>>
>> I am not sure I follow, can you please elaborate. Are you saying
>> that for example in the listing use case we don’t want the filtered
>> diagnostics? In other words it should be u...
2016 May 04
4
Filter optimization remarks by the hotness of the code region
This idea came up a few times recently [1][2] so I’d like start prototyping it. To summarize, we can emit optimization remarks using the -Rpass* options. These are currently emitted by optimizations like vectorization[3], unrolling, inlining and since last week loop distribution.
For large programs however this can amount to a lot of diagnostics output to sift through. Filtering this by the
2016 Jun 27
0
Filter optimization remarks by the hotness of the code region
...ltering, but should
>>>> pass the relative hotness information to the frontend. Given that
>>>> these diagnostics are not just going to be used for -Rpass and
>>>> friends, but also for generating reports by other tools (see the
>>>> discussion around D19678, for example), I think it is important to
>>>> allow the frontend to filter.
>>>
>>> I am not sure I follow, can you please elaborate. Are you saying
>>> that for example in the listing use case we don’t want the filtered
>>> diagnostics? In other...