From Fedora Project Wiki

< Changes

Revision as of 11:36, 25 January 2017 by Jkurik (talk | contribs) (→‎Current status)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)



Switch GCC in Fedora 26 to 7.x.y, rebuild all packages with it, or optionally rebuild just some packages with it and rebuild all packages only in Fedora 27.


Current status

Detailed Description

GCC 7 is currently in stage3, will move to stage4 on January 19th, in prerelease state with only regression bugfixes and documentation fixes allowed. The release will happen probably in the middle of April. We are working on scratch gcc rpms and will perform a test mass rebuild.

Benefit to Fedora

See for the list of changes.


All packages should be rebuilt with the new gcc once it hits f26, or, if there is not enough time for that, just all packages built after the new gcc hits the buildroots.

  • Proposal owners:

Build gcc in f26, rebuild packages that have direct dependencies on exact gcc version (libtool, llvm, gcc-python-plugin, odb).

  • Other developers: First few days/weeks just voluntary rebuilds using the new system gcc, if things fail, look at and fix bugs in packages or, if there is a gcc bug or suspected gcc bug, analyze and report.
  • Release engineering: Organize a mass rebuild, either in f26 or in f27
  • Policies and guidelines: No policies need to be changed

Upgrade/compatibility impact

No impact

How To Test

GCC has its own testsuite, which is run during the package build, plus many other packages with automated tests also help to test the new gcc.

User Experience

Users will be able to see compiled code improvements and use the newly added features. Developers will notice a newer compiler, and might need to adjust their codebases acording to, or, if they detect a GCC bug, report it.


libtool, gcc-python-plugin, odb, llvm depend on exact gcc version, those need to be rebuilt.

Contingency Plan

If bugs are discovered, I'd appreciate help from the package owners in preparing self-contained testcases to speed up analysis and fixing the bugs. Don't have time to debug issues in 12000+ packages, especially when in many cases it could be caused by undefined code in the packages etc. I don't expect we'll have to fall back to the older gcc, we've never had to do it in the past, but worst case we can mass rebuild everything with older gcc again.

  • Contingency mechanism: Revert to older gcc, mass rebuild everything again
  • Contingency deadline: Before release
  • Blocks release? Yes
  • Blocks product? No


Release Notes

Fedora 26 comes with GCC 7.1 as primary compiler, see for user visible changes in it.