How to profile compile times of a source code?

Stefan Koch uplink.coder at googlemail.com
Sat Jan 30 23:34:50 UTC 2021


On Saturday, 30 January 2021 at 22:47:39 UTC, Ahmet Sait wrote:
> I'm looking for ways to figure out what parts of the code slows 
> down the compiler other than brute force trial.
>
> Can I use -vtemplates switch for this?
> Would -v (verbose) switch helpful in some way?
> How would I know if my bottleneck is ctfe or templates?
> How do the compiler devs approach this issue?
>
> I'm interested in all kinds of tricks to the point of debugging 
> the compiler itself although anything less complicated would be 
> appreciated.

I have a way of getting the profile data your are after.
Get the dmd_tracing_20942 branch from 
https://github.com/UplinkCoder/dmd
Compile that version of dmd.
this special version of dmd will generate a trace file which can 
be read with the included printTraceHeader tool



More information about the Digitalmars-d-learn mailing list