[llvm-dev] Next steps for optimization remarks?

[Hal Finkel via llvm-dev]

On 06/27/2017 01:48 PM, Brian Gesiak via llvm-dev wrote:
> Adam, thanks for all the suggestions!
>
> One nice aspect of the `-Rpass` family of options is that I can filter 
> based on what I want. If I only want to see which inlines I missed, I 
> could use `clang -Rpass-missed="inline"`, for example. On the other 
> hand, optimization remark YAML always include remarks from all passes 
> (as far as I can tell), which increases the amount of time it takes 
> opt-viewer.py and other tools to parse. Would you be open to including 
> options to, for example, only emit optimization remarks related to 
> loop vectorization, or to not emit any analysis remarks? Or is it 
> important that the YAML always include all remarks?

I don't object to adding some kind of filtering option, but in general 
it won't help. An important goal here is to provide analysis (and other) 
tools to users that present this information at a higher level. The 
users won't, and shouldn't, know exactly what kinds of messages the 
tools use. This is already somewhat true for llvm-opt-report, and will 
be even more true in the future.

  -Hal

>
> Let me know what you think! In the meantime, I'll try to add the 
> progress bar you mention in llvm.org/PR33522 
> <http://llvm.org/PR33522>. Thanks!
>
> - Brian Gesiak
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

-- 
Hal Finkel
Lead, Compiler Technology and Programming Languages
Leadership Computing Facility
Argonne National Laboratory

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170628/81b56e80/attachment.html>