Re: parrot cvs mirrored with svk

2004-08-27 Thread Robert Spier
This now lives at http://svn.perl.org/parrot/cvs/ (use guest/guest) http://svn.perl.org/viewcvs/parrot/cvs/trunk/ It is updated from CVS once an hour. Have fun! -R At Sat, 7 Aug 2004 09:52:30 +0100, Chia-liang Kao wrote: [1 text/plain; us-ascii (7bit)] Hi, I've just setup a

Re: NCI Tests Failing

2004-08-27 Thread Leopold Toetsch
Joshua Gatcomb wrote: This might help shed some light: $ cd t/pmc $ parrot nci_1.pasm Not really. bash: parrot: command not found ;) You got an old parrot around somewhere in the path? $ parrot --gc-debug nci_1.pasm Segmentation fault (core dumped) Well, I just don't have these segfaults. Wait

Re: Compile op with return values

2004-08-27 Thread Leopold Toetsch
Steve Fink wrote: On Aug-26, Leopold Toetsch wrote: .sub @regex_at_foo_imc_line_4711 # e.g. Yes, this illustrates what I was really getting at. My compiler can certainly take a subroutine name (or file and line number, or whatever) to use to generate the code with, but what is the proper way to

Re: NCI Tests Failing

2004-08-27 Thread Dan Sugalski
At 10:06 AM +0200 8/27/04, Leopold Toetsch wrote: Joshua Gatcomb wrote: $ parrot --gc-debug nci_1.pasm Segmentation fault (core dumped) Well, I just don't have these segfaults. Wait ... Oops, I've turned on incremental GC here, which could make it succeed. Recompiling ... another coffee ... No.

Re: [perl #31346] [PATCH] tests and fixes for Undef PMC

2004-08-27 Thread Dan Sugalski
At 1:43 PM -0700 8/26/04, Bernhard Schmalhofer (via RT) wrote: This patch adds some test for the Undef PMC. Apparently not -- the patch wasn't included... -- Dan --it's like this--- Dan Sugalski

Re: NCI Tests Failing

2004-08-27 Thread Joshua Gatcomb
--- Leopold Toetsch [EMAIL PROTECTED] wrote: Joshua Gatcomb wrote: This might help shed some light: $ cd t/pmc $ parrot nci_1.pasm Not really. bash: parrot: command not found ;) You got an old parrot around somewhere in the path? No - believe it or not I only ever keep 1 version

Re: parrotbench.pl - massive update (smaller update)

2004-08-27 Thread Dan Sugalski
At 8:15 AM -0700 8/26/04, Joshua Gatcomb wrote: I found a few and have erradicated them. I also added some new functionality. You can now switch between CPU time and real (wall-clock) time Applied, thanks. -- Dan --it's like

Re: [perl #31302] NCI GC issues

2004-08-27 Thread Leopold Toetsch
Dan Sugalski [EMAIL PROTECTED] wrote: Current CVS parrot looks to be losing track of NCI PMCs. Once a DOD run goes they get swept collected up, which is a Bad Thing. I think I could track it down. It wasn't strictly NCI related, though. The split of dynamic loaders init/load code caused an

Re: NCI Tests Failing

2004-08-27 Thread Joshua Gatcomb
--- Dan Sugalski [EMAIL PROTECTED] wrote: I can trigger the problem locally, though not with the nci tests. (And, indeed, it may not be the NCI tests ultimately at fault) The core dump shows things dying in the dod run. GDB's backtrace is: Dan Ok, I tracked it down to a CVS change of

Pathological Register Allocation Scenarios

2004-08-27 Thread Gregor N. Purdy
Dan -- I think it would be interesting to find out how, say, gcc behaves on the pathological code structures you've run into. Could your compiler spit out a structurally (although not semantically! :) equivalent piece of C code that could be used with a C compiler to see how we do vs. C compilers

Re: [perl #31302] NCI GC issues

2004-08-27 Thread Joshua Gatcomb
--- Leopold Toetsch [EMAIL PROTECTED] wrote: I think I could track it down. It wasn't strictly NCI related, though. I guess you didn't need me to track down the CVS changes as this fixed the problem - THANKS. Cheers Joshua Gatcomb a.k.a. Limbic~Region

Re: NCI Tests Failing

2004-08-27 Thread Leopold Toetsch
Dan Sugalski [EMAIL PROTECTED] wrote: I can trigger the problem locally, though not with the nci tests. (And, indeed, it may not be the NCI tests ultimately at fault) The core dump shows things dying in the dod run. It's fixed. See answer to your ticket. leo

Re: NCI Tests Failing

2004-08-27 Thread Dan Sugalski
At 3:32 PM +0200 8/27/04, Leopold Toetsch wrote: Dan Sugalski [EMAIL PROTECTED] wrote: I can trigger the problem locally, though not with the nci tests. (And, indeed, it may not be the NCI tests ultimately at fault) The core dump shows things dying in the dod run. It's fixed. See answer to your

Re: [perl #31302] NCI GC issues

2004-08-27 Thread Leopold Toetsch
Joshua Gatcomb wrote: I guess you didn't need me to track down the CVS changes Well, I just started updating some slides for tomorrows Perl workshop in Bupapast: http://www.perl.org.hu/english/ changed a single line of code and got a segfault in the slide presentation program (slpod.imc). The

Re: [perl #31292] [PATCH classes/unmanagedstruct.pmc] Don't Share Nested Structs Across Parents

2004-08-27 Thread chromatic
On Mon, 2004-08-23 at 03:17, Leopold Toetsch via RT wrote: I'd rather not have the cloning in the C code. If you don't reuse the nested structure descriptor, it's wasting resources. There could be another property that tells how many times someone is using it. I don't think you will like

Add functions in dynext to the extending interface?

2004-08-27 Thread Mattia Barbon
Hello, should they be? I think they are covered by the statemente in pdd11 (... about the same level of access to Parrot that bytecode programs ...). Regards Mattia