CTFE Status

[Stefan Koch via Digitalmars-d]

I have an update about ctfe performance.
I wondered for quite a while why newCTFE had a 5 millisecond 
overhead, when compared the old interpreter.
Since on my charts it had comparable or better stats.
I finally figured it out.

Because the interpreter is supposed to be ctfe-able itself it 
uses a gc-allocated stack.
And that in turn call envokes the gc.
The mark phase of the garbage-collector matches up exactly with 
the extra time taken.

I have no idea, why this happens though since the GC is supposed 
to be disabled.