Re: [perl #37906] socklen_t not defined

2006-02-28 Thread David Dyck
On Sun, 26 Feb 2006 at 07:31 -0800, Bernhard Schmalhofer via RT...: From: Bernhard Schmalhofer via RT <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Date: Sun, 26 Feb 2006 07:31:10 -0800 Subject: [perl #37906] socklen_t not defined Hi David, why does parrot expect socklen_t to be defined? Since

Parrot vs NekoVM

2006-02-28 Thread Nicolas Cannasse
Hi list, 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://ncannasse.free.fr/?p=66). I would like to unde

Rare failure of t/dynoplibs/myops alarm sequence

2006-02-28 Thread Tim Bunce
FYI I saw this once but haven't been able to repeat it: t/dynoplibs/myopsok 6/7 # Failed test (t/dynoplibs/myops.t at line 107) # got: '1 # alarm1 # 2 # alarm2 # 3 # alarm3 # alarm1 # alarm3 # alarm3 # 4 # alarm3 # alarm3 # 5 # don

Re: Parrot vs NekoVM

2006-02-28 Thread Leopold Toetsch
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

Announcing "Amber for Parrot 0.4.2 (Argument)"

2006-02-28 Thread Roger Browne
I have released "Amber for Parrot" version 0.4.2 (Argument): Downloads: http://xamber.org/download.html Release history: http://xamber.org/history.html Project home page: http://xamber.org/index.html "Amber for Parrot" is an Eiffel-like scripting language for the Parrot Virtual Machine. Changes

Re: Rare failure of t/dynoplibs/myops alarm sequence

2006-02-28 Thread Leopold Toetsch
On Feb 28, 2006, at 14:59, Tim Bunce wrote: FYI I saw this once but haven't been able to repeat it: t/dynoplibs/myopsok 6/7 This can happen if the machine is busy. leo

Re: NCI 'v' vs '' in function parameter signatures

2006-02-28 Thread Tim Bunce
On Tue, Feb 14, 2006 at 10:04:59PM +0100, Leopold Toetsch wrote: > On Feb 14, 2006, at 18:29, Tim Bunce wrote: > > >The runtime dlfunc code will need to be altered to normalize away the > >trailing v so old code won't break. Should it warn about that? > > Yes, a warning please. Here's the patch.

Re: svn performance

2006-02-28 Thread Andy Dougherty
> On Fri, Feb 17, 2006 Andy Dougherty wrote: [svn co on Solaris 8 is painfully *slow*] > $ time wget http://cvs.perl.org/snapshots/parrot/parrot-latest.tar.gz > > real0m16.84s > user0m0.09s > sys 0m0.20s > > $ time svn co http://svn.perl.org/parrot/trunk parrot-trunk > > real 2:0

Re: Parrot vs NekoVM

2006-02-28 Thread Jonathan Worthington
"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

Re: Parrot vs NekoVM

2006-02-28 Thread Nicolas Cannasse
> > 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

Re: Parrot vs NekoVM

2006-02-28 Thread Joshua Isom
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

Re: Rare failure of t/dynoplibs/myops alarm sequence

2006-02-28 Thread Tim Bunce
On Tue, Feb 28, 2006 at 03:37:23PM +0100, Leopold Toetsch wrote: > > On Feb 28, 2006, at 14:59, Tim Bunce wrote: > > >FYI I saw this once but haven't been able to repeat it: > > > >t/dynoplibs/myopsok 6/7 > > This can happen if the machine is busy. Okay. Can't the test be ma

Valgrind Reports Useful?

2006-02-28 Thread chromatic
Hi there, I just managed to get Valgrind working on my Linux PPC box. Are Valgrind (memcheck, cachegrind, etc) reports useful from various platforms? If so, is there a good example PIR file to run that stresses sufficient code (or should someone add a new testgrind target that collects these

Re: Valgrind Reports Useful?

2006-02-28 Thread Will Coleda
Running "make test" in languages/tcl should be pretty painful. On Feb 28, 2006, at 5:13 PM, chromatic wrote: Hi there, I just managed to get Valgrind working on my Linux PPC box. Are Valgrind (memcheck, cachegrind, etc) reports useful from various platforms? If so, is there a good exampl

Re: Valgrind Reports Useful?

2006-02-28 Thread chromatic
On Tuesday 28 February 2006 14:19, Will Coleda wrote: > Running "make test" in languages/tcl should be pretty painful. Some tests will fail (STDERR is different), but you can set $ENV{VALGRIND} and anything that uses Parrot::Test will run it. Nifty. -- c

Re: [perl #38627] [TODO] fill Parrot_register_move() with code

2006-02-28 Thread Karl Forner
On 2/25/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > > Leopold Toetsch (via RT) wrote: > > > fill the function body of Parrot_register_move() (src/utils.c 633 ff). > > Parrot is now using this function [1] for recursive tailcalls. There are > 2 new tests in t/compilers/imcc/imcpasm/optc.t. > >