On Thu, Jul 17, 2003 at 12:58:12PM -0400, Dan Sugalski wrote:
The first is done in the case of readw or writew, for example. The
second for event-driven programs that set up callbacks and park
themselves forever in one big ProcessEvent call. (Tk programs come to
mind) The third is to be
On Thu, Jul 17, 2003 at 03:53:45PM -0700, Tim Howell wrote:
I've got some extra time to spend on Parrot in the next few months and
I'd really like to get involved. I have decent C and perl skills.
Where would I be most useful?
Having answered a few of these queries, each time in a somewhat
# New Ticket Created by Lars Balker Rasmussen
# Please include the string: [perl #23025]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=23025
There's no reason to test for the presence of setenv/unsetenv in libc
-
# New Ticket Created by Lars Balker Rasmussen
# Please include the string: [perl #23027]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=23027
I've added a way to add or remove options on a per-c-file basis.
Right
# New Ticket Created by Lars Balker Rasmussen
# Please include the string: [perl #23028]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=23028
(but not on Solaris/SPARC...)
t/op/stacks.NOK 11# Failed test
# New Ticket Created by Lars Balker Rasmussen
# Please include the string: [perl #23029]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=23029
-Wpadded seems to be more trouble than it's worth at this stage, so I
# New Ticket Created by Jürgen Bömmels
# Please include the string: [perl #23034]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=23034
Hi,
During searching for memory leaks and hunting bugs only visible on
MacOS, I
Hello,
What happend to the tinderboxens? ATM only two are running:
galactic-tcc and adrastea.
adrastea is not very useful because its disk is full
about to cvs checkout parrot:
cvs [checkout aborted]: cannot write CVS/Entries.Backup: No space left on device
cvs checkout complete
galactic-tcc
At 11:15 GMT 18.07.03, Juergen Boemmels [EMAIL PROTECTED] wrote:
: This is the state of the tinderboxens for the last week or so.
: Does anybody actually look at the tinderboxens?
i run mine (slug) by hand once a day (when i remember), since
i use the snapshots rather than cvs. i'm running one
Benjamin Goldberg [EMAIL PROTECTED] wrote:
Not the next instruction ... the next *branch* instruction. And only
replace those branch instructions which could be loops.
Works. Many thanks for the input.
I have now running this:
1) Initialization:
- normal core: build op_func_table with
Leopold Toetsch [EMAIL PROTECTED] writes:
JüRgen BöMmels [EMAIL PROTECTED] wrote:
QUESTION: The calling convention for methods states that P2 should be
the object the sub was called on. The current build_call_frames pushes
the object starting at P5. How can the NCI-Interface be extended to
On Fri, Jul 18, 2003 at 12:15:37PM +0200, Juergen Boemmels wrote:
This is the state of the tinderboxens for the last week or so.
Does anybody actually look at the tinderboxens?
I generally look at them every other day or so, but normally only
through my summarizer interface
I've added Steve's response to the
Experimental Parrot Wiki
http://www.vendian.org/parrot/wiki/
Which, of course, has a link to his Tinderbox summary. Hmm... perhaps a
little tinderbox weather report line should appear on the wiki main page?
There are also links to CVS histories, and LXR,
At 12:15 PM +0200 7/18/03, Juergen Boemmels wrote:
Hello,
What happend to the tinderboxens? ATM only two are running:
galactic-tcc and adrastea.
I just gave glastig a thump, though only the base (non-JIT) test
build stuff. It's too short of disk space for anything else,
unfortunately. I'll see
At 2:59 PM -0700 7/17/03, Damien Neil wrote:
On Thu, Jul 17, 2003 at 12:58:12PM -0400, Dan Sugalski wrote:
The first is done in the case of readw or writew, for example. The
second for event-driven programs that set up callbacks and park
themselves forever in one big ProcessEvent call. (Tk
OK, this should be fixed in CVS -- I just added/subtracted 1 as
appropriate so that the test is no longer sensitive to whether
0 == -0 (since this wasn't what we were supposed to be testing here).
Simon
Dan Sugalski [EMAIL PROTECTED] wrote:
Events should be checked and processed in several instances:
3) When we do a quick check to see if there are pending events to be processed
I have now a patch ready, which does 3) without additioal performacne
penalty for all cores except JIT.
(A short
At 6:01 PM +0200 7/18/03, Leopold Toetsch wrote:
Dan Sugalski [EMAIL PROTECTED] wrote:
Events should be checked and processed in several instances:
3) When we do a quick check to see if there are pending events to
be processed
I have now a patch ready, which does 3) without additioal
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #23039]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=23039
OK here it is.
Again the description for the record:
1) Initialization:
-
On Thu, 17 Jul 2003, Dan Sugalski wrote:
At 9:24 AM +0200 7/17/03, Leopold Toetsch wrote:
Simon Glover [EMAIL PROTECTED] wrote:
For instance, in findclass, you have:
if (VTABLE_get_pmc_keyed(interpreter, interpreter-class_hash,
Of course, if you apply the previous patch, you'll also need to apply
this one...
Simon
--- MANIFEST.oldFri Jul 18 13:35:04 2003
+++ MANIFESTFri Jul 18 13:35:41 2003
@@ -1861,6 +1861,7 @@
t/pmc/managedstruct.t []
t/pmc/multiarray.t
# New Ticket Created by Jürgen Bömmels
# Please include the string: [perl #23040]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=23040
Hi,
finally I found one of the double free errors in io.c:
At Parrot_exit the
On Fri, Jul 18, 2003 at 12:04:39PM -0400, Simon Glover wrote:
OK, this should be fixed in CVS
Yup.
--
Lars Balker RasmussenConsult::Perl
At 1:34 PM -0400 7/18/03, Simon Glover wrote:
Of course this still doesn't work, because we never actually add anything
to the class_hash. Patch below fixes this, as well as various bugs in
Parrot_single_subclass, and adds a couple of regression tests.
Thanks Simon. Applied.
--
At 5:51 PM + 7/18/03, J¸rgen Bmmels (via RT) wrote:
i,
finally I found one of the double free errors in io.c:
At Parrot_exit the PIOs are destroyed and the buffer memory is
freed. Unfortunatly the pointer is not cleared, so if there is a
second PMC pointing to the same PIO the buffer is
# New Ticket Created by Jürgen Bömmels
# Please include the string: [perl #23044]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=23044
nci.c generates a bunch of prototype warnings when compiled with gcc
and
On Fri, Jul 18, 2003 at 11:29:27AM -0400, Dan Sugalski wrote:
Nope, that won't work. A lot of what's done is really main thread
with interrupts and that doesn't map well to doing all signal
handling in separate threads. You really do want to pause the main
program to handle the events that
Damien Neil wrote:
[snip]
Also, given that asynchronous IO is a fairly unpopular programming
technique these days (non-blocking event-loop IO and blocking
threaded IO are far more common), I would think long and hard before
placing support for it as a core design goal of the VM. If there
is
brentdax core.ops is...monolithic.
Dan core.ops could use a good splitting out, definitely
At 108k, core.ops is the second largest file in the Parrot distribution.
It's larger than all but five or six C files in bleadperl. It has
nearly five hundred more lines than pp.c--and
BG == Benjamin Goldberg [EMAIL PROTECTED] writes:
BG Damien Neil wrote:
BG [snip]
Also, given that asynchronous IO is a fairly unpopular programming
technique these days (non-blocking event-loop IO and blocking
threaded IO are far more common), I would think long and hard before
On Fri, Jul 18, 2003 at 01:06:03PM -0700, Damien Neil wrote:
Also, given that asynchronous IO is a fairly unpopular programming
technique these days (non-blocking event-loop IO and blocking
threaded IO are far more common), I would think long and hard before
placing support for it as a core
Brent Dax:
# Since I don't think it's polite to flood peoples' mailboxes, I have
# uploaded the 205 kb (9213 line) patch to
# http://filespace.brentdax.com/brentdax/coresplit.diff.
The version I originally posted contained a patch to classes/timer.pmc,
basically disabling its guts. That was
With this increase in the number of files, I'm going to ask for
something I've thought of for a while, but not had the guts to ask for.
Could we try and clean up the parrot/ directory? Specifically, I'd like
all of the source code itself moved into a single subdirectory, leaving
at the toplevel
Maybe someone should write a script like this:
#!/usr/local/bin/perl -wlpi.bak
s/
(\$?\w+) \s* - \s* vtable \s* - \s* (\w+) \s*
\( \s* (interp\w*) \s* , \s* \1 \s*,
/VTABLE_$2($3, $1,/xg;
__END__
[untested]
Then run it on all the code, except that which actually defines
Benjamin Goldberg [EMAIL PROTECTED] writes:
(ChangeLog, Configure.pl, parrot.spec, and whatever else is really
needed to build and distribute parrot (make.pl?)).
Nothing is currently using make.pl, and it's way out of date compared
to the configure system - delete it?
--
Lars Balker Rasmussen
At 12:48 on 07/14/2003 +0200, Lars Balker Rasmussen [EMAIL PROTECTED] wrote:
I've taken this very simple approach to the problem. A perl-wrapper
for the CC lines in makefiles/root.in
.c$(O) :
$(PERL) tools/dev/cc_flags.pl $(CC) $(CFLAGS) ${cc_o_out}$@ -c $
I would go a bit
I can make such a change if you tell me exactly how it should be done.
(I am not a lawyer, so i don't want to do this inappropriately).
I'd think a safe first step would be to change any When this is
determined to Yet Another Society. But beyond that it gets fuzzy to
me.
--Josh
At 12:16
What happend to the tinderboxens? ATM only two are running:
galactic-tcc and adrastea.
I restarted the scripts on aniani. I'm at a loss as to why they stopped running.
-J
--
This might be a time to do a Tinderbox v2 rev. The current tinder
model works pretty well, but it's got some error identification
issues, and since it works in a fetch, build, test, sleep, repeat
mode if something goes horribly wrong the box stops. A cron-style
periodic fire-off job might be
39 matches
Mail list logo
