Re: Parrot Shootout

2005-12-12 Thread Brent Fulgham
-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

Re: Parrot Shootout

2005-12-12 Thread Leopold Toetsch
On Dec 12, 2005, at 9:29, Brent Fulgham wrote: Well, to be honest I've been adding them as you've posted them here or to SVN. If anyone objects to this, please let me know and I'll remove them immediately. I assume you are okay with them being posted to the shootout website under a BSD-styl

Re: Parrot Shootout

2005-12-12 Thread Leopold Toetsch
On Dec 12, 2005, at 0:38, Joshua Isom wrote: ... Oh, attached is fannkuch, works fairly well. Only about four seconds for me, three with an optimized build. And given that their machine's faster(and x86 linux as opposed to my ppc OSX), I think it's reasonable to say that parrot beats small

Re: [perl #37888] Latest changes break JIT on FreeBSD and OS X

2005-12-12 Thread Leopold Toetsch
On Dec 11, 2005, at 20:37, Joshua Isom (via RT) wrote: With the binarytrees test(Leo's modifications), using -j causes a seg fault on FreeBSD 5.4, and "invoke() not implemented in class 'SArray' current instr.: 'main' pc 135 (binarytrees.leo.pir:45)" on OS X. I'm using r10448 for both.

Library loading - no more duplicates

2005-12-12 Thread Leopold Toetsch
As of r10458 Parrot doesn't load_bytecode the same file [1] twice anymore. That is: load_bytecode 'foo.pir' load_bytecode 'foo.pasm' # silently ignored load_bytecode 'foo.pbc'# silently ignored load_bytecode 'bar/foo.pir'# ok [2] There is also an interface to query load

[perl #37898] [TODO] build parrot includes

2005-12-12 Thread via RT
# New Ticket Created by Leopold Toetsch # Please include the string: [perl #37898] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=37898 > Currently the files runtime/parrot/include/*.pasm are created during Configure. But

threads on Solaris aren't parallel?

2005-12-12 Thread Erik Paulson
Hi - I'm using an older version of Parrot (0.2.2) so I can use threads. It seems that Parrot on Solaris doesn't ever use more than one processor. The program attached should create argv[1] number of threads, and divide up over both of them argv[2] - ie perfect linear speedup. I've got a dual-pr

Re: Compiling Parrot with Visual C++ 2005

2005-12-12 Thread Ron Blaschke
Leopold Toetsch wrote: > On Dec 10, 2005, at 16:50, Ron Blaschke wrote: Here's a side by side comparison, Revision 10460, of Visual C++ 7.1 and 8.0. arithmetics.t suffers from -0.0 vs 0.0 problems. We've had something similar some time ago. They seem to have changed that in 8.0, as the test pas

Re: Compiling Parrot with Visual C++ 2005

2005-12-12 Thread jerry gay
On 12/12/05, Ron Blaschke <[EMAIL PROTECTED]> wrote: > Here's a side by side comparison, Revision 10460, of > Visual C++ 7.1 and 8.0. > great! > arithmetics.t suffers from -0.0 vs 0.0 problems. We've had something > similar some time ago. They seem to have changed that in 8.0, as the > test pass

Re: CREDITS where credit is due

2005-12-12 Thread Chip Salzenberg
On Sat, Dec 10, 2005 at 05:39:14PM -1000, Joshua Hoblitt wrote: > I'd like to propose that we change submissions.pod to ask that patch > submissions (at least from those without CI rights) include a new or > updated CREDITS entries with them. A pointer to CREDITS would be a good thing; just includ

Re: Bug or feature? Probably bug with macros

2005-12-12 Thread Chip Salzenberg
On Mon, Dec 12, 2005 at 12:30:47AM +0100, Leopold Toetsch wrote: > On Dec 11, 2005, at 23:45, Joshua Isom wrote: > >.IfDebug(1, > > print "var = " > > print var > >) > > As said, it was surprising me too. Anyway, I think typical use cases > are debugging and I prefer a solution that boils

Re: Library loading - no more duplicates

2005-12-12 Thread Chip Salzenberg
On Mon, Dec 12, 2005 at 01:16:35PM +0100, Leopold Toetsch wrote: > As of r10458 Parrot doesn't load_bytecode the same file [1] twice anymore. Neat - this is a fine approximate solution until we have real pbc hashing, and *may* continue to be necessary even with hashing, depending on whether we ca

[perl #37902] [PATCH] Visual C++ Compiler Tests and Options

2005-12-12 Thread via RT
# New Ticket Created by Ron Blaschke # Please include the string: [perl #37902] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=37902 > Attached patch adds a Configure test for Visual C++ compilers. For versions greater or

Re: Bug or feature? Probably bug with macros

2005-12-12 Thread Will Coleda
On Dec 12, 2005, at 1:55 PM, Chip Salzenberg wrote: On Mon, Dec 12, 2005 at 12:30:47AM +0100, Leopold Toetsch wrote: On Dec 11, 2005, at 23:45, Joshua Isom wrote: .IfDebug(1, print "var = " print var ) As said, it was surprising me too. Anyway, I think typical use cases are

Re: Bug or feature? Probably bug with macros

2005-12-12 Thread Chip Salzenberg
On Mon, Dec 12, 2005 at 02:07:41PM -0500, Will Coleda wrote: > On Dec 12, 2005, at 1:55 PM, Chip Salzenberg wrote: > >So I guess we just need a robust multi-line quoting convention (to > >pass multiple lines of code to macros). > > That sounds suspiciously like a HEREDOC. > > See: http://rt.perl.

Re: Bug or feature? Probably bug with macros

2005-12-12 Thread Roger Browne
On Mon, 2005-12-12 at 10:55 -0800, Chip Salzenberg wrote: > Forbidding commas in the expanded code is not OK So why not treat the comma as a delimiter only when either (1) It is on the same line as the start of the macro call, or (2) it appears alone on a line. The same rule can apply for the c

Re: Parrot Shootout

2005-12-12 Thread Leopold Toetsch
On Dec 8, 2005, at 6:53, Brent Fulgham wrote: Let the games begin! Another one: examples/shootout/pidigits.pir leo

[TODO] BigInt needs tests *badly*

2005-12-12 Thread jerry gay
as per leo, BigInt needs tests *badly*. BigInt also needs some design, as currently only gmp can be used to support BigInts. but i'll leave that for another ticket. ~jerry

Re: Bug or feature? Probably bug with macros

2005-12-12 Thread Joshua Isom
On Dec 12, 2005, at 12:55 PM, Chip Salzenberg wrote: Hm. Pondering... * PIR is primarily a compiler target, not a human language. (Pasm, in contrast, is an entirely non-human language.) So convenience is not paramount. But people will write in it. There are programmers who write

More shootout, two randoms

2005-12-12 Thread Joshua Isom
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 retrieving it 900,000 times. I have three versions written up. One that's split over two files, with on

Re: Parrot Shootout

2005-12-12 Thread Ed Peschko
On Sun, Dec 11, 2005 at 10:25:54PM +0100, Leopold Toetsch wrote: > > On Dec 11, 2005, at 17:01, Leopold Toetsch wrote: > > >Leopold Toetsch wrote: > > > >>I've timed Ack(3, 9) with an optimized Parrot build: > >>Python 13.7 > >>Parrot -j 15.3 > >>Parrot -C 13.8 > > > >Down now (r10445) a

Re: parrot directory reorganization (phase 2 mark 2)

2005-12-12 Thread jerry gay
On 12/10/05, jerry gay <[EMAIL PROTECTED]> wrote: > pf/ has been moved to src/packfile/, types/ to src/types/, and with a > little cleanup from leo due to a mistake i made (sorry!), ops/ has now > been moved to src/ops/. > > next on the list is io/. > io/ has been moved under src/io/. classes/ is n

Re: threads on Solaris aren't parallel?

2005-12-12 Thread Leopold Toetsch
On Dec 12, 2005, at 17:53, Erik Paulson wrote: Hi - I'm using an older version of Parrot (0.2.2) so I can use threads. It seems that Parrot on Solaris doesn't ever use more than one processor. [ ... ] Is there some way we can check to see if Parrot is actually creating more than one thr

[perl #37901] Make JIT smoke testing easy

2005-12-12 Thread via RT
# New Ticket Created by [EMAIL PROTECTED] # Please include the string: [perl #37901] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=37901 > --- osname= linux osvers= 2.4.26 arch= i486-linux cc= cc --- Flags: cat

Re: [perl #37901] Make JIT smoke testing easy

2005-12-12 Thread Alberto Simões
The patch file Parrot Assembler via RT wrote: Greetings, This message has been automatically generated in response to the creation of a parrotbug regarding: "Make JIT smoke testing easy" There is no need to reply to this message right now. Your ticket has been assigned an ID of [perl

Re: Parrot Shootout

2005-12-12 Thread Leopold Toetsch
On Dec 12, 2005, at 22:10, Ed Peschko wrote: Just curious, but why is mono at .38 seconds and 10.00 seconds respectively? What in the .NET implementation makes recursive calls so fast? Parrot function call and return sequence isn't really optimized yet. Currently I'm happy to be faster than

Re: Parrot Shootout

2005-12-12 Thread Leopold Toetsch
On Dec 8, 2005, at 6:53, Brent Fulgham wrote: Let the games begin! Another one has hit the svn repo: examples/shootout/nsieve-bits.pir Actually there are 2 versions: examples/shootout/nsieve-bits-2.pir The former cheats a bit by setting bits, the 2nd resets bits as of specs. le

What is PAST

2005-12-12 Thread Bernhard Schmalhofer
Leopold Toetsch schrieb: PAST isn't much more than 'hello.past'. When you search the p6i archives you'll find some messages about PAST and that it's up to HLL authors to specify the nodes and what not. In order to increase confusion, 'languages/punie' uses another PAST, which is kind of de

Re: threads on Solaris aren't parallel?

2005-12-12 Thread Jack Woehr
Leopold Toetsch wrote: There are AFAIK some issues with solaris (but I don't know the details) It might need a different threading lib or some additional init code to create 'real' threads. You just have to know how they implement pthreads, which is weasel-worded in POSIX and allows Solaris

Re: More shootout, two randoms

2005-12-12 Thread Leopold Toetsch
On Dec 12, 2005, at 21:55, 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 retrieving it 900,000 times. I have three versions writt

Re: Bug or feature? Probably bug with macros

2005-12-12 Thread Larry Wall
On Mon, Dec 12, 2005 at 11:14:32AM -0800, Chip Salzenberg wrote: : I still think heredocs were a botch for : Perl, which is generally not line-oriented. Hmm, well, the point is not so much whether Perl is line-oriented, but whether the *data* is line-oriented. The orientation of Perl is to go the

Re: More shootout, two randoms

2005-12-12 Thread Joshua Isom
I made the changes, adding the argv error handling(none of the docs state any necessity to handle no args so I'm not sure if it's necessary from their benchmarking point of view), and using ints when possible. If you were getting odd results, a difference between the c version and mine is the

[perl #37903] t/library/streams fails (test 14?)

2005-12-12 Thread via RT
# New Ticket Created by Alberto Simoes # Please include the string: [perl #37903] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=37903 > --- osname= darwin osvers= 8.0 arch= darwin-thread-multi-2level cc= cc --- Flag

parrot directory reorganization (phase 2 mark 3)

2005-12-12 Thread jerry gay
directory reorganization is nearly done. all directories on my list have been moved, save one; the only remaining directory to move is jit/. this will require some reworking of the jit configure system, and moving jit/ will also affect every platform (potentially in different ways (but hopefully no

Perl 6 Summary for 2005-12-05 through 2005-12-12

2005-12-12 Thread Matt Fowles
Perl 6 Summary for 2005-12-05 through 2005-12-12 All~ Welcome to another Perl 6 summary. This week, like last, Parrot has produced the highest volume of emails. Fine by me, Parrot tends to be easiest to summarize. This summary is brought to you by Snow (the latest soft toy in t

Re: parrot directory reorganization (phase 2 mark 3)

2005-12-12 Thread Joshua Hoblitt
On Mon, Dec 12, 2005 at 06:14:21PM -0800, jerry gay wrote: > specifically, joshua, when do you think you'll have tuits to dive into > the jit config system? no pressure--if it waits until next year, so be > it. i have some testing tasks i can keep busy with in the meantime. > based on that info, i

Re: [perl #37901] Make JIT smoke testing easy

2005-12-12 Thread Joshua Hoblitt
Applied as r10481. Thanks. -J -- On Mon, Dec 12, 2005 at 04:26:44PM +, Alberto Sim??es wrote: > The patch file > > Parrot Assembler via RT wrote: > >Greetings, > > > >This message has been automatically generated in response to the > >creation of a parrotbug regarding: > > "Make JIT smo

Re: [perl #37898] [TODO] build parrot includes

2005-12-12 Thread Joshua Hoblitt
There are actually two config tests that generate files under runtime/parrot/include. config/gen/parrot_include.pm config/auto/signal.pm I think that config/auto/signal.pm needs to stay as a config test as it's actually probing the system. Rerolling config/gen/parrot_include.pm as a CLI util sho

Re: Parrot Shootout

2005-12-12 Thread Joshua Isom
I've written up the fasta and knucleotide benchmarks. The knucleotide takes 25 seconds, but since their benchmark says it's given an argument of 2,500,000 and none of the programs use argv, and they all read from stdin, I'm assuming the 2,500,00 is for the fasta benchmark and it's output file.

Re: Parrot Shootout

2005-12-12 Thread Brent Fulgham
-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 sequence

Re: More shootout, two randoms

2005-12-12 Thread Brent Fulgham
-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

Re: More shootout, two randoms

2005-12-12 Thread Joshua Isom
There should be four attached files, the pair, random_single.pir, and random.pir. If parrot's executed in the same directory as the files, it'll work fine. On Dec 12, 2005, at 11:58 PM, Brent Fulgham wrote: Could you supply a single-file version with everything in it, along with your "incl

Re: [perl #37898] [TODO] build parrot includes

2005-12-12 Thread Leopold Toetsch
On Dec 13, 2005, at 4:52, Joshua Hoblitt wrote: There are actually two config tests that generate files under runtime/parrot/include. Please reread the text, e.g.: We should have plain Makefile rules instead, e.g.: runtime/parrot/include/iglobals.pasm: include/parrot/interpreter.h \

Re: Parrot Shootout

2005-12-12 Thread Leopold Toetsch
On Dec 13, 2005, at 5:06, Joshua Isom wrote: ... This brings me to a request, a sort opcode. The method I think would be best would be similar to perl's `sort {$a <=> $b} @array` syntax. $ perldoc src/classes/fixedpmcarray.pmc "METHOD void sort(PMC* cmp_func)" Sort this a

Re: [perl #37898] [TODO] build parrot includes

2005-12-12 Thread Joshua Hoblitt
On Tue, Dec 13, 2005 at 07:40:04AM +0100, Leopold Toetsch wrote: > > On Dec 13, 2005, at 4:52, Joshua Hoblitt wrote: > > >There are actually two config tests that generate files under > >runtime/parrot/include. > > Please reread the text, e.g.: Have you looked at what config/auto/signal.pm is a

Re: Parrot Shootout

2005-12-12 Thread Leopold Toetsch
On Dec 13, 2005, at 5:55, Brent Fulgham wrote: On Dec 12, 2005, at 12:23 PM, Leopold Toetsch wrote: Another one: examples/shootout/pidigits.pir The formatting on this is off. It looks like it's generating the sequence of digits, but it needs to be split into individual lines The progra

Re: More shootout, two randoms

2005-12-12 Thread Leopold Toetsch
On Dec 13, 2005, at 0:27, Joshua Isom wrote: I made the changes, adding the argv error handling(none of the docs state any necessity to handle no args so I'm not sure if it's necessary from their benchmarking point of view), and using ints when possible. Thanks. If you were getting odd re