[Activity] Week 37

2012-09-17 Thread Zhenqiang Chen 
Summary
* Workaround the unwind issue for shrink-wrap
* Verify Linaro tickets.

Details:
1. Debugging the failed cases for shrink-wrap. To workaround the
unwind issue, update arm_expand_epilogue to generate return not
simple_return when sp is changed.

2. Setup Linaro toolchain and verify 8 tickets:
*Linaro gcc:
lp:1036170: Function pointer dereferenced twice. It is ARM special bug
which is confirmed in 4.6, 4.7 and FSF trunk only on ARM.
lp:1048709: wrong assembler, out of range vldr instruction. Confirmed
in Linaro 4.6. Can not reproduce it in 4.7 or FSF 4.6.
lp:1014658: It is c++11 related issue in 4.6.
lp:944572: It is a gcc general issue.
lp:972503 and lp:1039401 can not be reproduced.

* Linaro binary toolchain:
lp:1046718: confirmed and fixed it.
lP:1049498: invalid

Plans:
* Prepare Linaro binary toolchain 2012.09 release.
* Performance test for shrink-wrap.
* Follow-up the tickets.

Best regards!
-Zhenqiang

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] report week 37

2012-09-17 Thread Peter Maydell 
Current Milestones:
||  || Planned|| Estimate   || Actual ||
|| clean up kvm-qemu cp i/f || 2012-09-20 || 2012-09-20 ||||
|| fake-trustzone   || 2012-10-15 || 2012-10-15 ||||
Also planned: general keeping up with kernel changes; upstream patch
review; qemu-linaro releases. May change dates to align with overall
KVM plan for the quarter when that is finalised.

Previous Milestones:
||cp15-rework   || 2012-01-06 || 2012-06-23 || 2012-06-24 ||
||a15-lpae-support  || 2012-07-13 || 2012-07-20 || 2012-07-20 ||

 == track-kvm-abi-changes ==
 * folded in Christoffer's interrupt ABI changes
 * updated to new ONE_REG ABI for register accesses
 * QEMU now in sync with the kernel patchset Christoffer has just sent to alkml
 == other ==
 * qemu-linaro 2012.09 released
 * various meetings/status calls

KVM blueprint progress tracker:
http://ex.seabright.co.nz/helpers/backlog?group_by=topiccolour_by=stateprojects=linaro-kvm

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: [ACTIVITY] report week 37

2012-09-17 Thread Michael Hope 
On 17 September 2012 21:21, Peter Maydell peter.mayd...@linaro.org wrote:
 Current Milestones:
 ||  || Planned|| Estimate   || Actual ||
 || clean up kvm-qemu cp i/f || 2012-09-20 || 2012-09-20 ||||
 || fake-trustzone   || 2012-10-15 || 2012-10-15 ||||
 Also planned: general keeping up with kernel changes; upstream patch
 review; qemu-linaro releases. May change dates to align with overall
 KVM plan for the quarter when that is finalised.

 Previous Milestones:
 ||cp15-rework   || 2012-01-06 || 2012-06-23 || 2012-06-24 ||
 ||a15-lpae-support  || 2012-07-13 || 2012-07-20 || 2012-07-20 ||

  == track-kvm-abi-changes ==
  * folded in Christoffer's interrupt ABI changes
  * updated to new ONE_REG ABI for register accesses
  * QEMU now in sync with the kernel patchset Christoffer has just sent to 
 alkml

Nice.  Does this check off cp15-kernel-qemu-interface?  And 'Resync
with a clean set of kernel headers from a tree based on kvm-next', or
is that post merge?

-- Michael

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: [Activity] Week 37

2012-09-17 Thread Zhenqiang Chen 
On 18 September 2012 07:04, Michael Hope michael.h...@linaro.org wrote:
 On 17 September 2012 19:49, Zhenqiang Chen zhenqiang.c...@linaro.org wrote:
 Summary
 * Workaround the unwind issue for shrink-wrap
 * Verify Linaro tickets.

 Details:
 1. Debugging the failed cases for shrink-wrap. To workaround the
 unwind issue, update arm_expand_epilogue to generate return not
 simple_return when sp is changed.

 Hmm.  An interesting case for shrinkwrap is:

 int foo(void *p) {
   char big-on-stack-object[543234];

   if (p == NULL) return -1;

   lots-of-code-that-causes-spills-and calls()
 }

 as shortcutting the prologue is where we get the saving.  Does the
 prologue normally touch SP, or is this for alloca() style functions
 only?

For spilling and alloca() style functions, prologue will touch SP.

For a local array, prologue will also touch SP if accessing the array
element. My logs show, gcc will generate code like

   sub sp, sp, #size of the array
   ...
   ldr r3, [sp, offset]


Thanks!
-Zhenqiang

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain