You may have noticed that I have created a new BZR/Launchpad branch for Linaro GCC 4.6:
lp:gcc-linaro/4.6
https://code.launchpad.net/~linaro-toolchain-dev/gcc-linaro/4.6
Up until now, this has not been buildable due to unfixed bugs. However, upstream GCC have now straightened out the problems, so I have pushed a buildable version into the branch.
I shall attempt to keep this branch as up-to-date as I can (at least, I will once the holiday season and January travel are over), but I'll only push updates if they build for me, so hopefully the branch should remain fairly stable, at least for our purposes.
Note that so far I've only tested build-ability. Right now I'm not making any promises about the quality of the compiler.
At some point, we'll want to use this branch to hold our own patches (both those that will never go upstream, and those that are queued for GCC 4.7), so it will diverge from upstream 4.6 a bit. For the moment, it's merely a mirror.
Andrew
On 18.12.2010 16:08, Andrew Stubbs wrote:
You may have noticed that I have created a new BZR/Launchpad branch for Linaro GCC 4.6:
lp:gcc-linaro/4.6
https://code.launchpad.net/~linaro-toolchain-dev/gcc-linaro/4.6
Up until now, this has not been buildable due to unfixed bugs. However, upstream GCC have now straightened out the problems, so I have pushed a buildable version into the branch.
I shall attempt to keep this branch as up-to-date as I can (at least, I will once the holiday season and January travel are over), but I'll only push updates if they build for me, so hopefully the branch should remain fairly stable, at least for our purposes.
Note that so far I've only tested build-ability. Right now I'm not making any promises about the quality of the compiler.
At some point, we'll want to use this branch to hold our own patches (both those that will never go upstream, and those that are queued for GCC 4.7), so it will diverge from upstream 4.6 a bit. For the moment, it's merely a mirror.
Andrew
Fyi, native gcc-4.6 packages based on upstream trunk, installable on maverick and natty can be found at
deb http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu maverick main deb-src http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu maverick main
The armel build should finish tomorrow. Testsuite results for arm and thumb mode are included in the build log and in the package's doc dir.
Issues on ARM are:
- gccgo build failure (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46958)
- gnat build failure https://launchpad.net/ubuntu/+source/gcc-snapshot/20101215-0ubuntu1/+build/2...
- quadmath support (needed, wanted?)
Matthias
On Sun, Dec 19, 2010 at 4:08 AM, Andrew Stubbs ams@codesourcery.com wrote:
You may have noticed that I have created a new BZR/Launchpad branch for Linaro GCC 4.6:
lp:gcc-linaro/4.6
https://code.launchpad.net/~linaro-toolchain-dev/gcc-linaro/4.6
Up until now, this has not been buildable due to unfixed bugs. However, upstream GCC have now straightened out the problems, so I have pushed a buildable version into the branch.
I shall attempt to keep this branch as up-to-date as I can (at least, I will once the holiday season and January travel are over), but I'll only push updates if they build for me, so hopefully the branch should remain fairly stable, at least for our purposes.
I build trunk once a week as part of the automated builds. How about I send you an email with the corresponding SVN revision on every successful build?
-- Michael
On 05/01/11 00:56, Michael Hope wrote:
I build trunk once a week as part of the automated builds. How about I send you an email with the corresponding SVN revision on every successful build?
I've just updated it to the state as of 31st December. Unfortunately there's a bug after that that prevents it cross-building.
Your tests wouldn't have picked that up, I think? However, if you let me know when you get a successful build that would certainly be useful information.
Thanks
Andrew
On Wed, Jan 5, 2011 at 10:55 PM, Andrew Stubbs ams@codesourcery.com wrote:
On 05/01/11 00:56, Michael Hope wrote:
I build trunk once a week as part of the automated builds. How about I send you an email with the corresponding SVN revision on every successful build?
I've just updated it to the state as of 31st December. Unfortunately there's a bug after that that prevents it cross-building.
Your tests wouldn't have picked that up, I think?
No, but I've been tempted to add a cross build a few times.
However, if you let me know when you get a successful build that would certainly be useful information.
Will do.
-- Michael
linaro-toolchain@lists.linaro.org
-
Andrew Stubbs -
Matthias Klose -
Michael Hope