-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 22, 2005, at 3:17 PM, peter baylies wrote:
Short version: uncomment lines 86-87, patch follows. I was hoping I
wouldn't need them, but I was wrong. This has been tested, and should
produce the correct output now.
--- mandelbrot.pir 200
FYI, the revised shootout updates are on the site:
http://shootout.alioth.debian.org/sandbox/benchmark.php?test=all&lang=parrot
Performance seems much better with the interpreter
flags suggested. Please let me know if you notice any problems.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 12, 2005, at 12:55 PM, Joshua Isom wrote:
Because the random benchmark is used for a few other tests, I
figured I'd do it next. To do it the same way in pir is slow
because it requires putting a variable into a global register and
retr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 12, 2005, at 12:23 PM, Leopold Toetsch wrote:
On Dec 8, 2005, at 6:53, Brent Fulgham wrote:
Let the games begin!
Another one: examples/shootout/pidigits.pir
The formatting on this is off. It looks like it's generating the
seq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 11, 2005, at 2:07 PM, Leopold Toetsch wrote:
On Dec 11, 2005, at 22:25, Leopold Toetsch wrote:
./parrot -C ack.pir4.9s
./parrot -C binarytrees.pir 1659.1s
And another f'up me: should we collect these shootout benchma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 9, 2005, at 12:26 AM, chromatic wrote:
Can a standard search path (e.g., DarwinPorts typical /opt/local/lib)
be included in parrots compile, or do I need to pass something to the
parrot interpreter at runtime?
As I read the code, this all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Do I need to pass compiler options to get SDL support? When I try to
use the tests in the examples directory, it can't seem to find my SDL
libraries and so forth.
Can a standard search path (e.g., DarwinPorts typical /opt/local/lib)
be inclu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 8, 2005, at 1:27 AM, Leopold Toetsch wrote:
On Dec 8, 2005, at 6:57, Brent Fulgham wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In addition to the shootout machine, I have a main development box
that runs Mac OS X (PowerPC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In addition to the shootout machine, I have a main development box
that runs Mac OS X (PowerPC). I attempted to build Parrot 0.4.0 on
this machine and encountered errors. The mailing list archive seems
to be down at the moment, so I could not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
A long while back someone made a request for people to create parrot
implementations of the shootout tests on Alioth (http://
shootout.alioth.debian.org). I wanted to let you know that I have
updated the shootout build machine with parrot (
> > Having thought about it a bunch more (because of this) I'm
> > proposing we let the compiler decide. The caller doesn't
> > know enough to make that decision.
>
> Read carefully. I said we *let* the caller decide, not *make* the
> caller decide. What, specifically, disturbs you about my
> > I think you may have missed the context of the message.
> > John was talking about creating his Alpha using various
> > existing projects that had already been done in C++.
>
> Why is he bothering? A year to produce a prototype doesn't
> seem like a useful way to expend effort on somethi
> Alan Burlison wrote:
>
> John Tobey wrote:
>
> > 1 November 2000 - Perl6 alpha in C++ that uses classes derived
> >from PerlInterpreter and SV
> everywhere in place
> >of these types, a la Pickle, but with inline
> >m
13 matches
Mail list logo
