Empy program running time

[bearophile]

Steven Schveighoffer:

> For example, D needs to call all the module ctors and do the import cycle  
> detection algorithm.

Even for an empty program?


> 0.11 seconds is not unreasonable.

It means about 170_000_000 CPU clock ticks, to me it seems a lot.


> But I'll also stress that timings at this precision can be fairly volatile.

I think this timing precision is not so bad.

Bye,
bearophile