On Aug 22, 2006, at 5:52 PM, John Siracusa wrote:
Has anyone looked at LLVM lately?
http://llvm.org/
I discovered it a few years ago. My personal interest is in the
portable C back end, so I can use the g++ compiler front end and send
the output through CodeWarrior or MPW compilers,
On 8/22/06, John Siracusa [EMAIL PROTECTED] wrote:
Has anyone looked at LLVM lately?
Yes, actually, I was looking at it just the other day. I couldn't get it to
build on x86-64, but I talked to some of the developers over in their IRC
channel, and they told me that this would be forthcoming
On 8/23/06, Aaron Sherman [EMAIL PROTECTED] wrote:
On 8/23/06, peter baylies [EMAIL PROTECTED] wrote:
On 8/22/06, John Siracusa [EMAIL PROTECTED] wrote:
Has anyone looked at LLVM lately?
[...]
On the other hand, Parrot built quite nicely on x86-64, although I think I
like the 32-bit
On 8/23/06, peter baylies [EMAIL PROTECTED] wrote:
On 8/22/06, John Siracusa [EMAIL PROTECTED] wrote:
Has anyone looked at LLVM lately?
[...]
On the other hand, Parrot built quite nicely on x86-64, although I think I
like the 32-bit build (which also built just fine, albeit without ICU)
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
John Siracusa wrote:
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.
Has anyone looked at LLVM lately?
http://llvm.org/
It seems to be making a lot of progress lately with the support of Apple
(which is using LLVM for its own purposes in Mac OS X). Is there anything
there Parrot can steal? Would it make sense for Parrot to target LLVM
bytecode and let LLVM do
