On Fri, 19 Aug 2011 01:29:05 -0400, Marco Leise wrote:
Am 29.07.2011, 17:23 Uhr, schrieb Steven Schveighoffer
:
On Fri, 29 Jul 2011 10:50:52 -0400, bearophile
wrote:
Steven Schveighoffer:
For example, D needs to call all the module ctors and do the import
cycle
detection algorithm.
Marco Leise:
> You think in the wrong category. Imagine where this would matter, where
> you would invoke a program multiple times.
I agree, and I think 0.11 seconds (on a slow PC) is a bit too much. I think
there is something smelly that will need tuning/optimization.
Bye,
bearophile
Am 29.07.2011, 17:23 Uhr, schrieb Steven Schveighoffer
:
On Fri, 29 Jul 2011 10:50:52 -0400, bearophile
wrote:
Steven Schveighoffer:
For example, D needs to call all the module ctors and do the import
cycle
detection algorithm.
Even for an empty program?
Yes. I bet even an empty
On Fri, 29 Jul 2011 10:50:52 -0400, bearophile
wrote:
Steven Schveighoffer:
For example, D needs to call all the module ctors and do the import
cycle
detection algorithm.
Even for an empty program?
Yes. I bet even an empty program has on the order of 50 module ctor/dtors
to run. A
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 t
On Fri, 29 Jul 2011 09:37:36 -0400, bearophile
wrote:
On an oldish Windows PC an empty C program generated by GCC takes about
0.03 seconds to run. An empty D2 program runs in about 0.11 seconds. Is
this expected/good/acceptable/fixable?
It is expected. A d program must initialize both t
On Fri, 29 Jul 2011 15:37:36 +0200, bearophile
wrote:
On an oldish Windows PC an empty C program generated by GCC takes about
0.03 seconds to run. An empty D2 program runs in about 0.11 seconds. Is
this expected/good/acceptable/fixable?
Bye,
bearophile
That's a lot better than I expect
On an oldish Windows PC an empty C program generated by GCC takes about 0.03
seconds to run. An empty D2 program runs in about 0.11 seconds. Is this
expected/good/acceptable/fixable?
Bye,
bearophile
