DMD与GDC相对于LDC [英] DMD vs. GDC vs. LDC

问题描述

不同的D编译器的优点/缺点是什么？如何实现性能和标准合规性/ D2支持？调试器支持有多好？错误消息有多好，是IDE集成？ 64位的支持有多好？我的想法到此为止：

What are the Pros/Cons of the different D Compilers? How is the performance and the standard compliance/D2 support? How well are debuggers supported? How good are the Error messages and is the IDE integration? How good is the 64 bit support? My thought so far:

DMD

• 成熟和维护良好


• 只有一个平台，64位支持不好


• 不是FOSS

GDC

• 支持各种平台
$ b $ b



• 已经非常成熟的优化， li>
  

• Supports various platforms
• Has very mature optimizations, so it's fast?
• Out of date runtime?
• GCC so a good debugger support?

LDC

• 支持各种平台


• LLVM，因此它支持JITing？


• 有非常成熟的优化，所以速度很快吗？


• 维护得不是很好。


• 过期的运行时？

• Supports various platforms
• LLVM, so it supports JITing?
• Has very mature optimizations, so it's fast?
• Not very well maintained?
• Out of date runtime?

死/不工作

dead/not working

• dang


• sdc


• MiniD - 非常非常好，但不是D（虽然从不声称是）

对于ARM，我认为GDC是首选工具，但我不确定。

I'm thinking about targeting ARM and i think GDC is the tool of choice, but I'm not sure.

推荐答案

DMD是参考实现。只有后端是专有的，前端是开源的。

代码生成的质量不是那么大。 x64支持只有几个月的时间。

DMD is the reference implementation. Only the backend is proprietary, the frontend is open source.
The code generation quality is not that overwhelming. x64 support is just a few months old though.

GDC和LDC都基于DMD前端，因此可能需要一些时间，直到新版本的前端合并。

由于后端使用的都非常成熟，这些编译器的质量主要取决于连接前端和后端的胶水代码。

GDC and LDC are both based on the DMD frontend so it might take some time until a new version of the frontend is merged in.
Since the backends they use are very mature and good the quality of these compilers mainly depends on the glue code which connects frontend and backend.

LDC和GDC仍然积极发展，但主要是只有几个人。

总之，他们可以使用一些人力。

LDC and GDC are still developed actively, but mainly by just a few guys.
All in all they could use some manpower.

这篇关于DMD与GDC相对于LDC的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！