What's blocking DDMD?

[Orvid King via Digitalmars-d]

On 7/22/2014 9:34 AM, Daniel Murphy wrote:> "Tourist"  wrote in message 
news:cmeqwpzglxjksmiekxbe at forum.dlang.org...
 >
 >> Just curious. I remember that there was some kind of a roadmap, but I
 >> cannot find it now.
 >
 > Nice timing, I was about to post a DDMD status message.
 >
 > As of a few hours ago DDMD has gone green in the autotester on the main
 > platforms.
 >
 > https://auto-tester.puremagic.com/?projectid=10
 >
 > Of the failing platforms:
 > OSX32: https://github.com/braddr/d-tester/pull/35 (OSX32 is crazy)
 > linux cross compilers: The tester machines currently have the wrong dmd
 > host toolchain installed.
 > win64: Same sort of thing as the linux cross compilers
 >
 > The autotester is showing a performance hit in the range of 25-50%
 > slower. Memory consumption appears to have a less significant increase.
 >
 > Also note that the autotester is only building ddmd in debug mode - the
 > dmd I'm comparing it against was built in release mode with full
 > optimizations.
 >
 > As for what's left:
 >> Fix cross-compilers/osx32
 >> Actually test and inevitably fix win64
 >> Finish reducing memory consumption/reinstating custom allocation
 >> schemes that I've disabled
 >> Merge, test and release.
 >
 > And then do the same things again for the other two backends.
 >
 > You can build it by following the instructions here:
 > https://github.com/D-Programming-Language/dmd/pull/3410
 >
 > If things go well I may release a DDMD zip that matches 2.066 for people
 > to try out.

I'd make a random guess at allocations being the difference in 
performance, DMD currently uses a bump-the-pointer allocator, which, if 
I'm remembering correctly, produced performance boosts of about that 
much when it was implemented.