Leopold Toetsch wrote:

Sebastian Riedel <[EMAIL PROTECTED]> wrote:



Sebastian Riedel wrote:





The attached version should do most of the things you wanted.





[EMAIL PROTECTED]:~/parrot$ tools/dev/parrotbench.pl -regex oo -conf
../parrotbench.conf
parrot perl python ruby
oo1 100% 39% 23% -
oo2 100% 40% 22% -



Good. Just some more notes:

I'd like the program to take a config like this:

parrot-C: ./parrot -C
parrot-j: ./parrot -j
perl:   /usr/bin/perl
perl-58_th: /opt/perl-th/bin/perl
...
scheme: /usr/bin/rep: .scm

that is to be able to compare more different programs. Timings should be
relative to the first given program.


The attached patch adds this, conf files now look so:

parrot: /home/sri/parrot/parrot: .pasm .imc
ruby: /usr/bin/ruby: .rb
python: /usr/bin/python: .py
python-C: /usr/bin/python -C: .py
perl: /usr/bin/perl -w: .pl

Output looks so (could be prettier):

[EMAIL PROTECTED]:~/parrot$ tools/dev/parrotbench.pl -b 'oo|addit' -e 'python|parrot|perl'
parrot(pasm) parrot(imc) python(py) perl(pl)
addit 100% 131% - 87%
addit2 - 100% - -
oo1 100% - 23% 39%
oo2 100% - 21% 39%



I studied the config system, and now i wonder if it would make sense
to write a configure step to probe for enemies, or is that overkill?


^^^^^^^
Please ...


Sorry, just kidding... everybody loves ruby!!! :)

No config step necessary. The -conf option is good enough.

leo



Cheers,
Sebastian

Attachment: parrotbench.patch.gz
Description: application/tgz



Reply via email to