>
> The patch attached tackles these two steps in the process. I'll apply
> it in 2-3 days unless someone objects, then proceed to step (3).
>
Patch applied to trunk in r24673.
In r24672, considerable refactoring of guts of runstep() to make it more
testable. This was done along same lines as in RT 43312
(config/auto/gmp.pm) and, in fact, some code in common was refactored
out into new Parrot module Parrot::Configure::Step::Methods. The stub
test file t/configure/144-au
On Monday 07 January 2008 12:05:43 Geoffrey Broadwell wrote:
> The problem is the -O and -j options, and their interaction with other
> things. -O (== -O1) and -O2 are both supposed to alter the default
> runcore selection (according to the running doc, at least). Turns out
> they don't, but it'
On Mon, 2008-01-07 at 11:51 -0800, chromatic via RT wrote:
> On Monday 07 January 2008 08:18:24 Geoffrey Broadwell wrote:
> > It seems like this should be available from interpinfo in PIR ... and
> > since 'parrot -v' displays optimization information, it should probably
> > display the runcore cho
# New Ticket Created by Stuart Jansen
# Please include the string: [perl #49490]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49490 >
Implement WIN & FAIL. Finish ifthen implementation. Add MEBBE test to
t/03-if.t
diff --
On Monday 07 January 2008 09:22:43 robby wrote:
> With skimming across the past 400 or so messages on this list I'm not
> exactly sure if this would be the correct list to post this, but I have
> a quick question regarding NCI's and callbacks.
>
> I've read http://www.parrotcode.org/docs/pdd/pdd16
With skimming across the past 400 or so messages on this list I'm not
exactly sure if this would be the correct list to post this, but I have
a quick question regarding NCI's and callbacks.
I've read http://www.parrotcode.org/docs/pdd/pdd16_native_call.htm and
nci.t and I haven't came up with
HAI
BTW Thanks, applied in r24660!
KTHXBYE
On Jan 7, 2008 11:50 AM, chromatic <[EMAIL PROTECTED]> wrote:
> On Monday 07 January 2008 08:18:24 Geoffrey Broadwell wrote:
>
> > There is no way from PIR to determine the current runcore, and it does
> > not appear in the output of 'parrot -v'. According to particle:
> >
> > *
> > in c you c
On Monday 07 January 2008 08:18:24 Geoffrey Broadwell wrote:
> There is no way from PIR to determine the current runcore, and it does
> not appear in the output of 'parrot -v'. According to particle:
>
> *
> in c you can look at interp->run_core, so you can find it with gdb easily
> it's easy
# New Ticket Created by Geoffrey Broadwell
# Please include the string: [perl #49480]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49480 >
There is no way from PIR to determine the current runcore, and it does
not appear
# New Ticket Created by Geoffrey Broadwell
# Please include the string: [perl #49458]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49458 >
examples/c/nanoparrot.c can be compiled with any of three different
runloops. The
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Jan 7 14:00:03 2008 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with mo
Allison Randal wrote:
François and I have been writing over each other's commits on
src/atomic/gcc_x86.c, so before I edit again, let's figure out the right
way to edit.
Andy, the headerizer dies with an error when src/atomic/gcc_x86.c has
two functions that are marked with both PARROT_API an
14 matches
Mail list logo
