On 8/23/06 4:09 PM, Aaron Sherman wrote: > here's the problem with that: llvm is a very light layer, but it's yet another > layer. To put it between parrot and hardware would mean that parrot is JITing > to LLVM byte-code, which is JITing to machine code. Not really ideal.
...unless LLVM does a much better job of native code generation than the existing Parrot code, that is. Optimization seems to be LLVM's "thing." -John
