(Add GCC9 feature page, sorry for the delay.) |
m (Add trackers) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 22: | Line 22: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1672505 #1672505] | ||
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/294 #294] | |||
== Detailed Description == | == Detailed Description == | ||
| Line 75: | Line 76: | ||
Fedora 30 comes with GCC 9.1 as primary compiler, see http://gcc.gnu.org/gcc-9/changes.html for user visible changes in it. | Fedora 30 comes with GCC 9.1 as primary compiler, see http://gcc.gnu.org/gcc-9/changes.html for user visible changes in it. | ||
[[Category: | [[Category:ChangeAcceptedF30]] | ||
[[Category:SystemWideChange]] | [[Category:SystemWideChange]] | ||
Latest revision as of 07:52, 5 February 2019
GCC9
Summary
Switch GCC in Fedora 30 to 9.x.y, rebuild all packages with it, or optionally rebuild just some packages with it and rebuild all packages only in Fedora 31.
Owner
- Name: Jakub Jelínek
- Email: jakub@redhat.com
- Product:
- Responsible WG:
-->
Current status
- Targeted release: Fedora 30
- Last updated: 2019-01-21
- Tracker bug: #1672505
- Release notes tracker: #294
Detailed Description
GCC 9 is currently in stage4 since January 7th, in prerelease state with only regression bugfixes and documentation fixes allowed. The release will happen probably in the middle of April. rpms have been built are since today in rawhide.
Benefit to Fedora
See http://gcc.gnu.org/gcc-9/changes.html for the list of changes.
Scope
All packages should be rebuilt with the new gcc once it hits f30, 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 f30, rebuild packages that have direct dependencies on exact gcc version (libtool, annobin, gcc-python-plugin).
- Other developers: First few days/weeks just voluntary rebuilds using the new system gcc, if things fail, look at http://gcc.gnu.org/gcc-9/porting_to.html and fix bugs in packages or, if there is a gcc bug or suspected gcc bug, analyze and report.
- Release engineering: . Mass rebuild requested for F30.
- 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 http://gcc.gnu.org/gcc-9/porting_to.html, or, if they detect a GCC bug, report it.
Dependencies
libtool, annobin, gcc-python-plugin 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. Jeff Law has performed test mass rebuild on x86_64.
- Contingency mechanism: Revert to older gcc, mass rebuild everything again
- Contingency deadline: Before release
- Blocks release? Yes
- Blocks product? No
Documentation
Release Notes
Fedora 30 comes with GCC 9.1 as primary compiler, see http://gcc.gnu.org/gcc-9/changes.html for user visible changes in it.