Hi,
To minimise the impact of the switch to Linaro toolchain 1109, I am tracking gcc tip code and building Android tip code against it, which, with the aim of finding and fixing problems as early as possible, is part of BP https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-integra.... These activities will keep going until gcc 1109 is released on 15th September.
The current revno of gcc 4.6 is 106800, whose code can be downloaded by running "bzr branch lp:gcc-linaro/4.6" and whose build can be found at https://android-build.linaro.org/builds/~chaoyang/android-gcc-4.6-code-tip-w... . The gcc build has already been patched with http://people.linaro.org/~bernhardrosenkranzer/gcc-4.6-11.08-bug50116.patch http://people.linaro.org/~bernhardrosenkranzer/gcc-4.6-11.08-bug50266.patch
The various Android builds against gcc 4.6 tip build can be found below. The builds for panda and leb-panda have been tested and both of them work fine.
[beagle] https://android-build.linaro.org/builds/~chaoyang/beagle/
[leb-snowball] https://android-build.linaro.org/builds/~chaoyang/leb-snowball/
[leb-imx53] https://android-build.linaro.org/builds/~chaoyang/leb-imx53/
[leb-origen] https://android-build.linaro.org/builds/~chaoyang/leb-origen/
[leb-panda] -- verified working fine https://android-build.linaro.org/builds/~chaoyang/leb-panda/
[panda] -- verified working fine https://android-build.linaro.org/builds/~chaoyang/panda/
Should you have any problems, please feel free to let me know. Thanks.
Regards
On Fri, Sep 09, 2011 at 02:17:29PM +0100, Chao Yang wrote:
To minimise the impact of the switch to Linaro toolchain 1109, I am tracking gcc tip code and building Android tip code against it, which, with the aim
Good job on proactively looking for bustage. I assume you guys worked out a plan with Michael on how to provide feedback on the issues we find -- let me know if that needs work.
When you say "gcc tip code" above, I think you actually mean "gcc-linaro tip code". Is that right?
The gcc build has already been patched with http://people.linaro.org/~bernhardrosenkranzer/gcc-4.6-11.08-bug50116.patch http://people.linaro.org/~bernhardrosenkranzer/gcc-4.6-11.08-bug50266.patch
For the sake of sanity, it may help to name those patches using "PR" instead of bug as they actually refer to GCC PRs.
Are those patches not going to make it into the 11.09 gcc-linaro spin?
On 9 September 2011 08:35, Christian Robottom Reis kiko@linaro.org wrote:
Good job on proactively looking for bustage. I assume you guys worked out a plan with Michael on how to provide feedback on the issues we find -- let me know if that needs work.
I presume normal bug reports will do the trick...
When you say "gcc tip code" above, I think you actually mean "gcc-linaro tip code". Is that right?
yes
The gcc build has already been patched with http://people.linaro.org/~bernhardrosenkranzer/gcc-4.6-11.08-bug50116.patch http://people.linaro.org/~bernhardrosenkranzer/gcc-4.6-11.08-bug50266.patch
For the sake of sanity, it may help to name those patches using "PR" instead of bug as they actually refer to GCC PRs.
OK with me -- I've symlinked them so new builds may use pr while old ones keep working.
Are those patches not going to make it into the 11.09 gcc-linaro spin?
Not sure - the bug is tracked in https://bugs.launchpad.net/gcc-linaro/+bug/827990 so the toolchain guys are aware of it.
Since the bug breaks our build, we need the fix in right now - so until it does get in, we're using the GCC_PATCH_URL mechanism to inject the patches.
ttyl bero
On Sat, Sep 10, 2011 at 7:15 AM, Bernhard Rosenkranzer bernhard.rosenkranzer@linaro.org wrote:
On 9 September 2011 08:35, Christian Robottom Reis kiko@linaro.org wrote:
Good job on proactively looking for bustage. I assume you guys worked out a plan with Michael on how to provide feedback on the issues we find -- let me know if that needs work.
I presume normal bug reports will do the trick...
When you say "gcc tip code" above, I think you actually mean "gcc-linaro tip code". Is that right?
yes
The gcc build has already been patched with http://people.linaro.org/~bernhardrosenkranzer/gcc-4.6-11.08-bug50116.patch http://people.linaro.org/~bernhardrosenkranzer/gcc-4.6-11.08-bug50266.patch
For the sake of sanity, it may help to name those patches using "PR" instead of bug as they actually refer to GCC PRs.
OK with me -- I've symlinked them so new builds may use pr while old ones keep working.
Are those patches not going to make it into the 11.09 gcc-linaro spin?
Not sure - the bug is tracked in https://bugs.launchpad.net/gcc-linaro/+bug/827990 so the toolchain guys are aware of it.
Since the bug breaks our build, we need the fix in right now - so until it does get in, we're using the GCC_PATCH_URL mechanism to inject the patches.
Yip, this patch will be in this weeks release. The fix was done in the upstream release branch and will come down as part of our monthly merge-from-trunk.
The merge request for this is at: https://code.launchpad.net/~ams-codesourcery/gcc-linaro/merge-from-fsf-20110...
The auto builder built it fine on i686, x86_64, A9, and ARMv5. The testsuite changes still need to be investigated.
Bernhard has done the right thing and pulled the upstream patch to meet their immediate need.
-- Michael
-
Bernhard Rosenkranzer -
Chao Yang -
Christian Robottom Reis -
Michael Hope