I ran my usual set of benchmarks of libav compiled with the current gcc
releases (hand-written assembly disabled). The results are in this
spreadsheet:
https://docs.google.com/spreadsheet/ccc?key=0AguHvNGaLXy9dHExeWZ1YWZ1c0s2VnpJRkl2bVRPU2c
First the good news, almost everything is faster with 4.
Current Milestones:
|| || Planned|| Estimate || Actual ||
||cp15-rework || 2012-01-06 || 2012-06-23 || 2012-06-24 ||
||a15-lpae-support || 2012-07-13 || 2012-07-13 ||||
||clean-up-kvm-patches ||||||
On 6 July 2012 00:10, Michael Hope wrote:
> Hi Ramana. These are covered by the release process documentation but
> I thought I'd fill them out.
I've found another flaw with the script which means the 4.7 release
testing we've done is broken. Before leaving today I thought I'd do a
md5sum on the
On Fri, Jul 06, 2012 at 05:19:10PM +0100, Peter Maydell wrote:
> Current Milestones:
> || || Planned|| Estimate || Actual ||
> ||cp15-rework || 2012-01-06 || 2012-06-23 || 2012-06-24 ||
Wow. That's a lot of months off-plan! I like it that you have t
On 6 July 2012 19:00, Christian Robottom Reis wrote:
> On Fri, Jul 06, 2012 at 05:19:10PM +0100, Peter Maydell wrote:
>> Current Milestones:
>> || || Planned|| Estimate || Actual ||
>> ||cp15-rework || 2012-01-06 || 2012-06-23 || 2012-06-24 ||
>
> W
Thanks for doing this yet again.
On 6 July 2012 16:52, Mans Rullgard wrote:
> I ran my usual set of benchmarks of libav compiled with the current gcc
> releases (hand-written assembly disabled). The results are in this
> spreadsheet:
> https://docs.google.com/spreadsheet/ccc?key=0AguHvNGaLXy9dHE
RAG
Amber: 4.7 2012.07 source release for reasons described below.
Green : 4.6 2012.07 source release done.
== Progress ==
* Worked on auto-inc-dec scheduler changes.First cut patch looking reasonable.
* Committed the neon permute intrinsics upstream.
* Release week : release tarballs prepare
