Release gcc 6

Asked by David Brown

gcc 6 has been available for a few months now, and has a number of very significant improvements that could be of benefit to embedded ARM users (optimiser improvements, warning improvements, and C++ language improvments).

But the milestone for releasing version 6 of the gnu arm embedded toolchain is not targeted until the end of the year, and contains one blueprint marked "slow progress" and one bug that has been delayed for nearly two years. While I am sure that both these points would be nice to have sorted, they cannot be good reason for delaying a gcc 6 build.

If these two points were put on hold, is there any reason why a gcc 6 release cannot be made now rather than waiting another 8 weeks?

Question information

English Edit question
GNU Arm Embedded Toolchain Edit question
No assignee Edit question
Solved by:
Thomas Preud'homme
Last query:
Last reply:
Revision history for this message
Best Thomas Preud'homme (thomas-preudhomme) said :

I've disconnected them from our 2016Q4 release: these are not blockers for the release. The release will be made by the end of the year as for other major release though. A major release always involve significant amount of work and this cannot be rushed without proper testing.

Best regards.

Revision history for this message
David Brown (davidbrown) said :

OK. Thanks for that answer. I realise there is a good deal of testing and other work involved in a release - I was just worried that that effort could not be undertaken until after these two (minor, IMHO) issues had been handled.

Revision history for this message
David Brown (davidbrown) said :

Thanks Thomas Preud'homme, that solved my question.

Revision history for this message
Freddie Chopin (freddie-chopin) said :

If you are interested in a toolchain with GCC 6, then you may want to try my bleeding-edge-toolchain version:

Revision history for this message
David Brown (davidbrown) said :

Thanks for that link, Freddie. I will give your build a try as soon as I get the time. I usually stick to more "official" builds for actual customer projects, but "bleeding edge" versions are great for learning about what is coming and for pre-project work.

(Thank you for making these builds available. I also know that you make binary builds for openocd for Windows, which I have used in the past.)