Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Currently the latest version of gcc available for RHEL8 is gcc 9.2.1 (https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/developing_c_and_cpp_applications_in_rhel_8/gcc-toolset-9_toolsets)
At the same time RHEL7 provides gcc 9.3.1 in Developers Toolset 9.1 (https://access.redhat.com/documentation/en-us/red_hat_developer_toolset/9/html/9.1_release_notes/dts9.1_release#Changes_in_DTS)

RHEL8 should provide gcc 9.3 to at least be not behind RHEL7

Version-Release number of selected component (if applicable):
Name         : gcc-toolset-9
Version      : 9.0
Release      : 4.el8
Architecture : x86_64
Size         : 10 k
Source       : gcc-toolset-9-9.0-4.el8.src.rpm

Unfortunately we would need a clear justification for updating the compiler.  The most recent reply from Siemens says "It doesn't make sense to use a faulty tool" -- that is not enough to justify an update, particulary at this stage in DTS 9's lifecycle.

We would need to know specifically what Siemens thinks is faulty.  ie, a testcase that is mis-compiled or which gives a incorrect diagnostic that is critical to Siemens so that we could fully evaluate the request.

User tells they would like 9.3.1 to match https://vfxplatform.com/ specification.

Otherwise, while not experiencing any specific issue, there is
https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=9.3

Paulo, the standard cycle for DTS is a .0 major release in the fall and a .1 bugfix release in the spring.   Further updates beyond those are restricted to major security issues or mission critical customer/partner bugfixes.  Neither of the two justifications in c#7 would be considered sufficient by engineering or product management to issue an additional DTS release.

The next planned DTS release is DTS 10 which will include gcc-10.x and is due out this fall.