# New Ticket Created by chromatic
# Please include the string: [perl #44229]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44229 >
Profiling some of the PGE tests reveals that our register allocation is fairly
expensive.
I want to get rid of this flag, and move the special case of DOD marking into
the mark() vtable entry. Here's a patch which accomplishes most of this
(except for getting rid of the special case) and breaks Tcl's PMCs
spectacularly.
A little patch review here would be swell.
-- c
=== src/pmc/
From: [EMAIL PROTECTED]
Date: Sat, 28 Jul 2007 11:54:40 -0700 (PDT)
-If a I is provided, Parrot automatically performs the equivalent
of
-a C operation on the given subroutine, and pushes the resulting
+If a I is provided, Parrot automatically performs the equivalent of
+a C ope
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sat, 28 Jul 2007 16:30:22 -0400
From: "jerry gay" <[EMAIL PROTECTED]>
Date: Sat, 28 Jul 2007 08:35:01 -0700
. . .
Parrot::Distribution offers a number of subroutines which allow one to
specify which subset of parrot f
On 2007-07-26 19:57:08 -0500, [EMAIL PROTECTED] ("Patrick R.
Michaud") said:
# New Ticket Created by "Patrick R. Michaud"
# Please include the string: [perl #44183]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44183 >
W
# New Ticket Created by Eric Wilhelm
# Please include the string: [perl #44213]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44213 >
Index: docs/faq.pod
===
On Saturday 28 July 2007 15:00:18 James E Keenan wrote:
> So, in principle, we can and should reduce the number of tests in 'make
> test' and hence reduce its running time. But that requires *all* of us
> -- not just ptc and me -- to be more diligent about running the
> specialized testing target
From: James E Keenan <[EMAIL PROTECTED]>
Date: Sat, 28 Jul 2007 18:00:18 -0400
. . .
So, in principle, we can and should reduce the number of tests in 'make
test' and hence reduce its running time. But that requires *all* of us
-- not just ptc and me -- to be more diligent ab
Paul Cochrane wrote:
As a short term improvement of the situtation, how would a "make
test-cage" target sound? This would be the same as "make test" but
with the coding standards (and any other cage-cleanliness-checking
tests) shifted into this suite, and not run by default with "make
test".
On Jul 28, 2007, at 12:54 PM, Will Coleda wrote:
Since I found myself doing this for PGE::Codestring and now for Tcl's
'__stringToList', I thought it might be a good idea to write down the
process in case anyone else finds themselves working on a similar
task.
http://www.perlfoundation.org/
From: "jerry gay" <[EMAIL PROTECTED]>
Date: Sat, 28 Jul 2007 08:35:01 -0700
On 7/28/07, Bob Rogers <[EMAIL PROTECTED]> wrote:
[sorry; forgot to attach the attachment.]
> As a step in that direction, is there an easy way to find out which
> coding standards tests should be applied
From: "jerry gay" <[EMAIL PROTECTED]>
Date: Sat, 28 Jul 2007 08:35:01 -0700
On 7/28/07, Bob Rogers <[EMAIL PROTECTED]> wrote:
> As a step in that direction, is there an easy way to find out which
> coding standards tests should be applied to a given source file? Some
> have "c_
Author: allison
Date: Sat Jul 28 12:17:33 2007
New Revision: 20290
Modified:
trunk/docs/pdds/draft/pdd25_concurrency.pod
Log:
[pdd] Added a note on concurrent runinterp.
Modified: trunk/docs/pdds/draft/pdd25_concurrency.pod
Author: pmichaud
Date: Sat Jul 28 11:54:40 2007
New Revision: 20289
Modified:
trunk/docs/pdds/pdd23_exceptions.pod
Log:
[docs]:
* Clarify the description of push_eh slightly.
Modified: trunk/docs/pdds/pdd23_exceptions.pod
==
Since I found myself doing this for PGE::Codestring and now for Tcl's
'__stringToList', I thought it might be a good idea to write down the
process in case anyone else finds themselves working on a similar task.
http://www.perlfoundation.org/parrot/index.cgi?how_to_convert_pir_to_c
Regards.
On 7/28/07, Bob Rogers <[EMAIL PROTECTED]> wrote:
>From: "Paul Cochrane" <[EMAIL PROTECTED]>
>Date: Sat, 28 Jul 2007 13:39:09 +0200
>
>. . .
>
>A longer term strategy would be to check for recently changed files
>(since the developer's last "svn up") and to run the coding standa
From: "Paul Cochrane" <[EMAIL PROTECTED]>
Date: Sat, 28 Jul 2007 13:39:09 +0200
. . .
A longer term strategy would be to check for recently changed files
(since the developer's last "svn up") and to run the coding standards
tests only over those files . . .
Paul
As a step i
On 28/07/07, chromatic <[EMAIL PROTECTED]> wrote:
> Let me preface this by saying that I know that our static analysis tests
> represent a tremendous amount of work by several people (especially Paul,
> with an enormous amount of respect to everyone who's contributed also to
> Perl::Critic and PPI)
18 matches
Mail list logo
