Linaro GCC 4.8-2014.03

Milestone information

Linaro GCC
Yvan Roux
Release registered:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata


Assigned to you:
No blueprints or bugs assigned to you.
No users assigned to blueprints and bugs.
No blueprints are targeted to this milestone.
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon gcc-linaro-4.8-2014.03.tar.xz (md5, sig) gcc-linaro-4.8-2014.03 sources 4,664
last downloaded 10 days ago
Total downloads: 4,664

Release notes 

The Linaro Toolchain Working Group is pleased to announce the 2014.03
engineering release of Linaro GCC 4.8.

As announced at Linaro Connect USA 2013 Linaro GCC is moving to a
pattern of quarterly stable releases, with engineering releases in the
intervening months. This is the second engineering release. The next stable
release will be the 2014.04 release.

Linaro GCC 4.8 2014.03 is the twelfth release in the 4.8 series. Based
off the latest GCC 4.8.3+svn208264 release, it includes performance
improvements and bug fixes.

Interesting changes include:
* Updates to GCC 4.8.3+svn208264

The source tarball is available from:

Downloads are available from the Linaro Releases website:

More information on the features and issues are available from the
release page:

Mailing list:



Interested in commercial support? Inquire at


View the full changelog

r208576 | yroux | 2014-03-14 20:48:42 +0100 (ven., 14 mars 2014) | 1 line

Make Linaro GCC gcc-linaro-4.8-2014.03.
r208471 | yroux | 2014-03-11 07:54:00 +0100 (mar., 11 mars 2014) | 2 lines

Merge from branches/gcc-4_8-branch up to rev 208264.

r207762 | yroux | 2014-02-13 16:06:33 +0100 (jeu., 13 févr. 2014) | 1 line

Bump version number, post release.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.