search for: pr33523

...se 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 sort of binary encoding of YAML would speed up parsing but I haven’t researched this topic yet... I added progress indicators in https://reviews.llvm.org/D34735, and it seems like it takes a while for the Python scripts to read some of the larger YAML files produced for m...

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

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