On Fri, Mar 11, 2011 at 6:43 PM, Vasily Chekalkin wrote:
> For the record. I'm implementor of original "switch based MULTI
> optimization". It improved math op performance 500%. Just because
> PCC+MMD are extremely slow and put additional pressure on GC.
If we don't want to do multi-dispatch (for
For the record. I'm implementor of original "switch based MULTI
optimization". It improved math op performance 500%. Just because
PCC+MMD are extremely slow and put additional pressure on GC.
--
Bacek
On Sat, Mar 12, 2011 at 10:30 AM, Jonathan "Duke" Leto
wrote:
> Howdy,
>
> Correctness wins ov
Howdy,
Correctness wins over performance every time, so I am +1 for this
branch to merge.
Duke
On Fri, Mar 11, 2011 at 3:17 PM, Peter Lobsinger wrote:
> On Fri, Mar 11, 2011 at 5:57 PM, Jonathan "Duke" Leto
> wrote:
>> Howdy,
>>
>> Peter, can you comment on the possible performance-related ch
On Fri, Mar 11, 2011 at 5:57 PM, Jonathan "Duke" Leto wrote:
> Howdy,
>
> Peter, can you comment on the possible performance-related changes
> that this branch could cause?
We took a small hit for the indirection NCI caused. We're not doing
that anymore, so it should be a little faster.
MULTIs t
Howdy,
Peter, can you comment on the possible performance-related changes
that this branch could cause?
Have you done any benchmarks?
Duke
On Fri, Mar 11, 2011 at 2:35 PM, Peter Lobsinger wrote:
> The pmc2c-multi-nativepccmethod branch changes the implementation of
> MULTIs in .pmc files from
The pmc2c-multi-nativepccmethod branch changes the implementation of
MULTIs in .pmc files from NCI to NativePCCMethod. This means that
these now handle their own PCC, in stead of rellying on NCI thunks to
accomplish this. These can now be modified to access a more broad
range of PCC functionality.
Howdy,
This was originally sent to parrot-directors, but I haven't seen any
movement on it, so I am forwarding it to parrot-dev.
There are some very important bits of feedback in here that I think
are very important for us to address.
Anybody have tuits to throw at this?
Duke
-- Forwa
On Thu, 10 Mar 2011, Gerd Pokorra wrote:
> There was reported a problem, when using
>
> load_language 'JSON'
>
> in the file "tools/dev/nci_thunk_gen.pir".
>
> I can not reproduce the error. According to the suggestion of cotto I
> created a branch. I called the branch "gerd/JSON_nqp".
>
> A
"Jonathan \"Duke\" Leto" writes:
> The most important thing now is to improve our ideas pages:
>
> https://www.socialtext.net/perl5/gsoc
>
> If TPF would like to use a different page, please let me know soon,
> since org apps cannot be modified after 11pm PST today.
With the wiki at https://www.
I have started an overhaul of the Parrot project ideas page already.
I've converted project ideas listed there previously into proper
templates that show most of the information fields we will need to
have. I've removed a few inappropriate ideas and added a few new
ideas. I'm adding ideas that I am
Howdy,
Sorry for the confusion, I had some emergency travel recently and have
not spread the word properly.
rafl++ has stepped up to be the org admin for The Perl Foundation this
year, I will help him with the transition.
I will be the org admin for Parrot Foundation this year.
I have already a
On Fri, Mar 11, 2011 at 4:46 AM, Reini Urban wrote:
> 2011/2/7 Jonathan Leto :
>> Howdy,
>>
>> Who wants to help with GSoC 2011 ?
>
> Hi,
> Deadline is today. Is the TPF applying?
> I saw nothing on p5p and tpf-gsoc, only here,
> but I assume Duke is again applying for us.
> Right?
>
> If not we'd
Am 10.03.2011 15:46, schrieb Jonathan "Duke" Leto:
Why is the Revision = 1 ?
Isn't that always the case now, and git_describe being the interesting
"number"?
Cheers,
Moritz
___
http://lists.parrot.org/mailman/listinfo/parrot-dev
2011/2/7 Jonathan Leto :
> Howdy,
>
> Who wants to help with GSoC 2011 ?
Hi,
Deadline is today. Is the TPF applying?
I saw nothing on p5p and tpf-gsoc, only here,
but I assume Duke is again applying for us.
Right?
If not we'd need an emergency plan.
> -- Forwarded message --
> Fr
14 matches
Mail list logo
