At 9:31 AM + 12/15/04, Leopold Toetsch via RT wrote:
Dan Sugalski wrote:
Or not. (I've got too many versions of parrot around at the moment) I
see this bug happening against yesterday morning's parrot.
imcc/CVS/Entries shows a date of Mon Dec 13 12:19:33 2004 for reg_alloc.c.
I still can't r
Dan Sugalski wrote:
Or not. (I've got too many versions of parrot around at the moment) I
see this bug happening against yesterday morning's parrot.
imcc/CVS/Entries shows a date of Mon Dec 13 12:19:33 2004 for reg_alloc.c.
I still can't reproduce it. CVS fetches either to P16 or even P3 for the
At 8:48 AM -0500 12/14/04, Dan Sugalski wrote:
At 9:08 AM + 12/14/04, Leopold Toetsch via RT wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
IMCC's doing odd things when moving PMCs into the appropriate spot
when calling into functions with a large number of parameters. Here's
a snip from a t
At 9:08 AM + 12/14/04, Leopold Toetsch via RT wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
IMCC's doing odd things when moving PMCs into the appropriate spot
when calling into functions with a large number of parameters. Here's
a snip from a trace of one of the programs running. Note the l
# New Ticket Created by Dan Sugalski
# Please include the string: [perl #33032]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=33032 >
IMCC's doing odd things when moving PMCs into the appropriate spot
when calling into
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> IMCC's doing odd things when moving PMCs into the appropriate spot
> when calling into functions with a large number of parameters. Here's
> a snip from a trace of one of the programs running. Note the lines
> from bytecode offset 78123, 78126, and 78130.
