On Fri, Aug 01, 2008 at 12:47:28AM +0200, Moritz Lenz wrote:
> Joshua Hoblitt wrote:
> > Since llvm-gcc uses the gcc front end this isn't surprising.
>
> Considering that perl 5 doesn't work with XS modules when compiled with
> llvm-gcc, I think it's at least worth to mention ;-)
I didn't say i
Since llvm-gcc uses the gcc front end this isn't surprising. In fact, if
parrot failed to build with that compiler it would only tell us that there is
something wrong with their intergration work. IMHO it would be more
interesting to test with clang which might actually pick up some sort of
porta
Joshua Hoblitt wrote:
> Since llvm-gcc uses the gcc front end this isn't surprising.
Considering that perl 5 doesn't work with XS modules when compiled with
llvm-gcc, I think it's at least worth to mention ;-)
> In fact, if
> parrot failed to build with that compiler it would only tell us that t
As a followup I added a line to PLATFORMS, as particle and Coke requested.
I also ran the benchmark tests with an optimized build both with
llvm-gcc 4.2 and ordinary gcc 4.2, here is what I get:
ordinary gcc:
real1m29.733s
user1m22.489s
sys 0m7.024s
llvm-gcc:
real1m55.984s
user
On Thursday 31 July 2008 13:53:21 Moritz Lenz wrote:
> rurban ask on IRC if somebody already tested parrot with llvm-gcc. So I
> just tried it out, and, *miracle*, it actually worked. Without any
> modifications.
>
> Just a
> make realclean; perl Configure.pl --cc=llvm-gcc && make test
> yields
> A
