[Mono-list] Announce: A .NET assembly -> native code generation tool (ala ngen for MONO)

Paolo Molaro lupus@ximian.com
Thu, 1 Aug 2002 13:40:17 +0200

On 08/01/02 Fergus Henderson wrote:
> There's no point trying to duplicate all of GCC's optimizations in your
> JIT compiler; doing that would be a huge amount of code duplication.
> It's much better to reuse GCC's optimizer, as Zoltan has done.
> Note also that GCC's optimizer has already been ported to a lot more
> architectures than the mono JIT has been.  For architectures where
> the choice is to use an interpreter or an ahead-of-time compiler,
> the ahead-of-time compiler should give a very significant speedup.

The jit is needed for several things anyway, you can't do without it,
even if you have an ahead-of-time compiler.
And there are several cases where the JIT can do better than any
ahead-of-time compiler, even if it does less optimizations, simply
beacuse it can do things based on assumptions you can make at runtime


lupus@debian.org                                     debian/rules
lupus@ximian.com                             Monkeys do it better