What's blocking DDMD?

[Daniel Murphy via Digitalmars-d]

"H. S. Teoh via Digitalmars-d"  wrote in message 
news:mailman.136.1406040115.32463.digitalmars-d at puremagic.com...

> Hmm. We should run a profiler to find out where the performance hit is
> coming from. It should be interesting, since presumably, your script to
> translate dmd to D basically generates the D equivalent of the C++ code,
> so major performance differences would point us to areas that need
> improvement in D.

I don't think any of it is caused by D itself (except maybe some druntime 
startup/shutdown overhead).  I think it's all coming from the memory 
allocation strategies I changed to get it working and haven't finished 
changing back, and from using different optimization settings/optimizer when 
compiling.

> > 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.
>
> Oh. Could that be the reason for the performance hit?

I'm sure that's part of it.

> One thought that occurred to me -- once the autotester goes green on all
> platforms, we should probably have the autotester include ddmd testing
> on all dmd PR's, so that during the transition period the C++ and D
> changes will be fully in sync.

That's exactly the plan.