search for: pr33522

...cluding 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? Let me know what you think! In the meantime, I'll try to add the progress bar you mention in llvm.org/PR33522. Thanks! - Brian Gesiak -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170627/2000005c/attachment.html>

...rt, and will be even more true in the future. Ah, I see, that makes sense. Thanks! > On Tue, Jun 20, 2017 at 1:50 AM, Adam Nemet <anemet at apple.com> wrote: > > We desperately need a progress bar in opt-viewer. Let me know if you want to add it otherwise I will. I filed llvm.org/PR33522 for this. > > In terms of improving the performance, I am pretty sure the bottleneck is still YAML parsing so: > > - If PGO is used, we can have a threshold to not even emit remarks on cold code, this should dramatically improve performance, llvm.org/PR33523 > - I expect that some so...

Hello all, In https://www.youtube.com/watch?v=qq0q1hfzidg, Adam Nemet (cc'ed) describes optimization remarks and some future plans for the project. I had a few follow-up questions: 1. As an example of future work to be done, the talk mentions expanding the set of optimization passes that emit remarks. However, the Clang User Manual mentions that "optimization remarks do not really make