cpp-build-analyzer
cpp-build-analyzer copied to clipboard
MetanoKid
Analyzes MSVC C++ compilations with C++ Build Insights SDK
Unfortunately is not easy to create a simple reproducible case. It seems that SpecializationID is 0. I will try to look more into this.
! defaults to nanoseconds ! supports miliseconds and seconds
- [ ] look into a faster undordered map - for big files most of the time is spent on hashing and looking up in maps - [ ] use...
When the analysis fails (`BuildAnalyzer::Analyze`) we just return a `bool` to say whether it succeeded. The idea is to improve error messages because the analysis can fail before calling the...
If users want to perform the full analysis, they have to type `--analyze_all` (or add as many `--analyze_` options as desired). Can't we make this flag optional, and set by...
Example mangled name when analyzing a `CppBuildAnalyzer` `Debug|x64` trace: ??$_Seek_wrapped@V?$_Vector_iterator@V?$_Vector_val@U?$_Simple_types@PEAVTimelineEntry@@@std@@@std@@@std@@PEAPEAVTimelineEntry@@@std@@YAXAEAV?$_Vector_iterator@V?$_Vector_val@U?$_Simple_types@PEAVTimelineEntry@@@std@@@std@@@0@$$QEAPEAPEAVTimelineEntry@@@Z We're currently undecorating them in `src/AnalysisData/Utilities/CppBuildInsightsDataConversion.cpp`.
For now, exporters receive the `std::string` path to output their data. It would be useful to have them receive an `std::ostream` and let caller manage the creation of that stream.