[ACTIVITY] 18-22 March 2013
== Progress == - Worked on VRP based zero/sign extension elimination at tree level - Some regression test cases are failing; investigating them == Plan == - Analyse the reason for test case failure and fix them - Extend the code to handle all the possible cases (currently implemented for subset to get the framework working) ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Week 12
Summary: * Send out shrink-wrap related patches for review. * Investigate how to add a new tree code. Details: 1. Fix lp:1157050 and lp:1107659 for Linaro toolchain binaries. 2. Test shrink-wrap dwarf/unwind info and send out the patches for review. 3. Make progress on conditional compare support. With some hard-codes in gcc, it can gimplify a small case to conditional compare on tree and no assert until expand. Plan: * Investigate how to expand conditional compare GIMPLE to RTL and emit asm. Planned leaves: * March 31. * April 4-8. Best Regards! -Zhenqiang ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] 18-22 March 2013
== Progress == - Looking at TLS relocs and coming up with test cases for garbage collecting them. - Patch for missedout testcases in gc section is up streamed. Thanks to Marcus. == Plan == - Complete gc section test cases for TLS relocs. - Understand and evaluate gprof support work for Aarch64 Misc - Leave on Wednesday and Thursday (27th and 28th) ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
RE: [ACTIVITY] Week 12
* Investigate how to expand conditional compare GIMPLE to RTL and emit asm. I think maybe we should start adding target specific expanders. Then all you need to do is take that expander and when you get a COND_EXPR and then looks at TRE provided information which then can exapnd the conditional compare without adding a new tree code. Note I think this should be discussed on the GCC list directly anyways rather than on the linaro form because it is more likely be accepted if talked about there. Thanks, Andrew From: linaro-toolchain-boun...@lists.linaro.org [linaro-toolchain-boun...@lists.linaro.org] on behalf of Zhenqiang Chen [zhenqiang.c...@linaro.org] Sent: Sunday, March 24, 2013 7:51 PM To: linaro-toolchain Subject: [ACTIVITY] Week 12 Summary: * Send out shrink-wrap related patches for review. * Investigate how to add a new tree code. Details: 1. Fix lp:1157050 and lp:1107659 for Linaro toolchain binaries. 2. Test shrink-wrap dwarf/unwind info and send out the patches for review. 3. Make progress on conditional compare support. With some hard-codes in gcc, it can gimplify a small case to conditional compare on tree and no assert until expand. Plan: * Investigate how to expand conditional compare GIMPLE to RTL and emit asm. Planned leaves: * March 31. * April 4-8. Best Regards! -Zhenqiang ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: [ACTIVITY] Week 12
On 25 March 2013 12:05, Pinski, Andrew andrew.pin...@caviumnetworks.com wrote: * Investigate how to expand conditional compare GIMPLE to RTL and emit asm. I think maybe we should start adding target specific expanders. Then all you need to do is take that expander and when you get a COND_EXPR and then looks at TRE provided information which then can exapnd the conditional compare without adding a new tree code. Note I think this should be discussed on the GCC list directly anyways rather than on the linaro form because it is more likely be accepted if talked about there. Thanks for the comments. The conditional compare mentioned here is a different from COND_EXPR. If my understanding is correct, COND_EXPR is for c1? v1: v2 conditional compare here is to represent the second operand of short-circuit, e.g. TRUTH_ANDIF_EXPR. It is more like c1? CMP (v1, v2): c1 It is just a CMP (GT, NE, etc)_EXPR if ignoring the conditional part. Agree with you, we should discuss it on GCC list. But before that, I want a prototype and estimate the efforts. Thanks! -Zhenqiang ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
