[cfe-dev] Clang: How to Analyse Compiletime of Templates?

[Dennis Luehring via cfe-dev]

i get this assertion (using latest Windows
Build(https://llvm.org/builds/) installer + VStudio extension)

1>Assertion failed: TimeTraceProfilerInstance == nullptr && "Profiler
should not be initialized", file
C:\src\llvm_package_2663a25f\llvm-project\llvm\lib\Support\TimeProfiler.cpp,
line 253
1>Stack dump:

assert in Function: void timeTraceProfilerInitialize(unsigned
TimeTraceGranularity)



Am 05.03.2020 um 20:22 schrieb Alexandre Ganea:
> Hi Dennis,
>
> Along with -ftime-trace, try either:
> - Clang Build Analyzer: https://aras-p.info/blog/2019/09/28/Clang-Build-Analyzer/
> - See++ Compiler Profiler: https://github.com/Viladoman/SeeProfiler
>
>
> -----Message d'origine-----
> De : cfe-dev <cfe-dev-bounces at lists.llvm.org> De la part de Dennis Luehring via cfe-dev
> Envoyé : March 5, 2020 2:16 PM
> À : cfe-dev at lists.llvm.org
> Objet : [cfe-dev] Clang: How to Analyse Compiletime of Templates?
>
> hello clang-devs,
>
> is clang able to help me to finde the most compiletime consuming templates in a 500KLOC app which uses a huge template library - something like a overview what templates are reasonable to optimize (in my case hide the template behind a specialized interface)
>
> i've read about /ftime
>
> https://aras-p.info/blog/2019/01/16/time-trace-timeline-flame-chart-profiler-for-Clang/
>
> but that seems no to help with template instanciation
>
> any advice?
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev