On Mar 5, 2006, at 18:33, Jonathan Worthington wrote:
"Leopold Toetsch" <[EMAIL PROTECTED]> wrote:
Mmm - actually -C needs computed goto, which isn't supported by all C
compilers.
Including the one that I produce the Win32 builds that I believe were
being tested with (MS Visual C++). Shouldn
"Leopold Toetsch" <[EMAIL PROTECTED]> wrote:
Mmm - actually -C needs computed goto, which isn't supported by all C
compilers.
Including the one that I produce the Win32 builds that I believe were being
tested with (MS Visual C++). Shouldn't it give a "we don't have a computed
goto runcore" err
On Mar 4, 2006, at 18:05, Nicolas Cannasse wrote:
-Cj does not produce different results than -j on the Win32 build of
Parrot. Is -Cj supported on this architecture ?
Yes, it should work. It might depend on, how fib is actually written in
PIR. As said this option is in a rather early state.
> $ time ./parrot -j fib.pir 30
> Fib(30): 1346269
>
> real0m4.774s
>
> Ok that's slow (AMD [EMAIL PROTECTED], unoptimized parrot build), you are
> right. But:
>
> $ time ./parrot -Cj fib.pir 30
> Fib(30): 1346269
-Cj does not produce different results than -j on the Win32 build of
Parrot.
On Feb 28, 2006, at 19:59, Nicolas Cannasse wrote:
Yes I understand that there is different cores for Parrot, but what are
the flags appropriate for doing some comparisons ? Some flags might do
very good in some cases and quite bad in some others. They might also
take tremendous time to JIT the
On Feb 28, 2006, at 1:59 PM, Nicolas Cannasse wrote:
On Feb 28, 2006, at 12:09, Nicolas Cannasse wrote:
Yesterday I did a quick fib(30) benchmark comparing Parrot Win32
daily
build (using jit core) and NekoVM (http://nekovm.org). The
results are
showing that Parrot is 5 times slower than N
The main flag sets for speed are -C, -Cj, -S, -Sj, -j, and sometimes
adding -Oc as well. On ppc, -C and -Cj are often the fastest. On x86,
-j is most often the fastest. But here's the cavaet, to use JIT, you
of course need someone to port it to that arch. With -C, your compiler
has to suppo
>
> On Feb 28, 2006, at 12:09, Nicolas Cannasse wrote:
>
>> Yesterday I did a quick fib(30) benchmark comparing Parrot Win32 daily
>> build (using jit core) and NekoVM (http://nekovm.org). The results are
>> showing that Parrot is 5 times slower than Neko (see my blog post on
>> this point there
"Nicolas Cannasse" <[EMAIL PROTECTED]> wrote:
Yesterday I did a quick fib(30) benchmark comparing Parrot Win32 daily
build (using jit core)
I'm guessing that's the build that I'm to blame for, and it's maybe worth
pointing out that it ain't an optimized build. But I think leo supplied the
re
On Feb 28, 2006, at 12:09, Nicolas Cannasse wrote:
Yesterday I did a quick fib(30) benchmark comparing Parrot Win32 daily
build (using jit core) and NekoVM (http://nekovm.org). The results are
showing that Parrot is 5 times slower than Neko (see my blog post on
this point there : http://ncann
10 matches
Mail list logo
