newCTFE Status July 2017

[Stefan Koch via Digitalmars-d]

On Monday, 31 July 2017 at 23:03:21 UTC, Temtaime wrote:
> On Sunday, 30 July 2017 at 20:40:24 UTC, Stefan Koch wrote:
>> On Thursday, 13 July 2017 at 12:45:19 UTC, Stefan Koch wrote:
>>> [...]
>>
>> Hello Guys,
>>
>> The bug preventing newCTFE from executing bf_ctfe[1] correctly
>>  (a peculiarity in which for for and if statement-conditions  
>> other then 32bit integers where ignored) is now fixed.
>>
>> [...]
>
> Aren't you disabling codegen by passing a -o- to your engine, 
> so it starts to compile faster?

Ah yes.
An oversight while posting the results. it does not affect the 
meassurements in any real way though the difference it 3-5 
milliseconds.

In the testcase the ctfe workload is totally dominant.