Howdy,
Our coverity scans are behind a login wall, according to
http://trac.parrot.org/parrot/wiki/Coverity .
How does one get access to it?
Duke
--
Jonathan "Duke" Leto
jonat...@leto.net
http://leto.net
___
http://lists.parrot.org/mailman/listinfo/p
Howdy,
I just added Cardinal to smolder.parrot.org and updated the setup.pir
and Rakefile to submit smoke reports to the right place.
Enjoy!
Duke
--
Jonathan "Duke" Leto
jonat...@leto.net
http://leto.net
___
http://lists.parrot.org/mailman/listinfo/p
As it stands it has got to go, but with love it might just be revived to
show deprecations as they come in, with appropriate workarounds.
We would need to formulate a policy on this.
Cheers, Michael (mikehh)
On 12 February 2011 01:27, Jonathan "Duke" Leto wrote:
> Howdy,
>
> This page needs l
Howdy,
This page needs love or needs to be deleted:
http://trac.parrot.org/parrot/wiki/Deprecation
Which one?
Duke
--
Jonathan "Duke" Leto
jonat...@leto.net
http://leto.net
___
http://lists.parrot.org/mailman/listinfo/parrot-dev
Howdy,
After discussion on #parrot, I unmerged the generational_gc branch
from master, it now lives in the gen_gc2 branch.
Duke
On Thu, Feb 10, 2011 at 1:50 PM, Vasily Chekalkin wrote:
> On Thu, Feb 10, 2011 at 11:56 PM, Nick Wellnhofer wrote:
>> This is really great work. What's especially i
I have re-enabled optimized register access for non-gcables in
5829c74. This mitigates some of the costs.
However, gcable register access is far from optimal. We have
annotations in the ops files to determine whether a register will be
written or not. A read-only GCable register access (by far the
There has been a marked decrease in performance on optimized builds
for some uses of Parrot since the merge of the generational_gc branch.
These stem from f14c1a62 ("Temporary workaround to enable write
barriering of CallContexts"). In brief, optimized access to registers
has been disabled.
2 case
