Document /d2cgsummary and other internal compilation metrics flags
There was a blog post by Aras Pranckevičius about an undocumented compiler flag /d2cgsummary. It would appear that the backend has the ability to report certain metrics that could possibly help diagnose unusual compilation times.
Slow compile times are a pain to figure out. Properly documenting these flags (and adding more!) could help us stay sane and happy.
It would be great to have more information. Knowing front end vs back end for compiling is nice, but still leaves a lot to be desired. ETW markers and/or more detailed breakdown would be great.
Andrew Pardoe [MSFT] commented
Thank you for creating this suggestion! This idea is under early development on our team. If you want to see this happen sooner, please upvote this suggestion.
Jonathan McDougall commented
Links to both the blog post and the reddit discussion are getting caught in the spam filter, so I can't post them here. You can check /r/cpp and look for the post on Aras' blog on 2017-10-23.