On 23 July 2016 at 16:24, Matthias Klumpp via Digitalmars-d-announce
> 3) Making LDC available for more architectures, or making GDC support a
> higher version of the Phobos standard library and build shared libraries.
> At time, LDC is the better fit because of shared library support and higher
> Phobos version. Current D projects are hard to compile with GDC because of
> the latter reason.
> More architectures are not per-se essential, but would be awesome to have.
> This feature request summarizes the status of arch support for D in free
> compilers: https://github.com/ldc-developers/ldc/issues/1636
Well, as GDC is supporting the last C++ release, the only next logical
step would be to get bootstrapping from 2.068 to 2.071 or whatever
version of the frontend has sufficiently ironed out all compatibility
This means that backporting compiler fixes and the standard library
from upstream is acceptably on the cards. It's just that the
feature-set will remain the same as 2.068.
> 5) Have hardening supported for the D compilers:
As per the wiki, if you use GDC then there's nothing for you to do.