2216808 – cmake: FortranC.Flags test fails under GCC Toolset 12

This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

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.

Bug 2216808 - cmake: FortranC.Flags test fails under GCC Toolset 12

Summary: cmake: FortranC.Flags test fails under GCC Toolset 12

Keywords:
Status:	CLOSED MIGRATED
Alias:	None
Product:	Red Hat Enterprise Linux 9
Classification:	Red Hat
Component:	cmake
Sub Component:
Version:	9.3
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	Tom Stellard
QA Contact:	qe-baseos-tools-bugs
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2023-06-22 17:06 UTC by Florian Weimer
Modified:	2023-09-22 16:40 UTC (History)
CC List:	1 user (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2023-09-22 16:40:58 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:
Flags:	pm-rhel: mirror+

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	RHEL-7395	0	None	Migrated	None	2023-09-22 16:40:53 UTC
Red Hat Issue Tracker	RHELPLAN-160510	0	None	None	None	2023-06-22 17:08:58 UTC

Description Florian Weimer 2023-06-22 17:06:04 UTC

Manually runnign the upstream testsuite from cmake-3.20.2-8.el9 under GCC Toolset 12

gcc-toolset-12-12.0-6.el9.x86_64
gcc-toolset-12-annobin-docs-11.08-2.el9.noarch
gcc-toolset-12-annobin-plugin-gcc-11.08-2.el9.x86_64
gcc-toolset-12-binutils-2.38-16.el9.x86_64
gcc-toolset-12-binutils-gold-2.38-16.el9.x86_64
gcc-toolset-12-dwz-0.14-4.el9.x86_64
gcc-toolset-12-gcc-12.2.1-7.4.el9.x86_64
gcc-toolset-12-gcc-c++-12.2.1-7.4.el9.x86_64
gcc-toolset-12-gcc-gfortran-12.2.1-7.4.el9.x86_64
gcc-toolset-12-gdb-11.2-4.el9.x86_64
gcc-toolset-12-libquadmath-devel-12.2.1-7.4.el9.x86_64
gcc-toolset-12-libstdc++-devel-12.2.1-7.4.el9.x86_64
gcc-toolset-12-runtime-12.0-6.el9.x86_64

results in a FortranC.Flags failure.  This happens with GCC 12 proper, too, and the following upstream patches are relevant:

commit 6a0ce19ce1cb594cdec19bacc9fc7a38156e38da
Author: Björn Esser <besser82>
Date:   Wed Jan 19 17:26:14 2022 +0100

    FortranCInterface: Fix compatibility with GCC gfortran 12 LTO
    
    Since version 12.0 the GCC Fortran compiler has implemented "WG5/N1942",
    which causes, if link-time opmization is enabled, obfuscation of hard-coded
    string values in the compiler objects and its resulting ELF-binaries.
    
    This causes the CMake-internal detection of the mangling scheme for the
    naming of subroutines to fail.  Thus we must ensure to have any link-time
    optimization features to be disabled on the executable file we perform the
    detection on.
    
    The static libraries, however, must be build with LTO and non-LTO objects,
    as that will ensure the verify step will operate on IPO objects, if building
    those is requested by the system compiler flags.
    
    Fixes: #23123
    
    Signed-off-by: Björn Esser <besser82>

commit cb616d43d6f0912f3b4ab61d210cebe42dbfffb3
Author: Brad King <brad.king>
Date:   Mon May 16 11:15:34 2022 -0400

    FortranCInterface: Fix failure with gfortran 12 and Clang
    
    The C flags added by commit 6a0ce19ce1 (FortranCInterface: Fix
    compatibility with GCC gfortran 12 LTO, 2022-01-19, v3.22.2~5^2)
    should only be added for the GNU C compiler.
    
    Fixes: #23500
    Issue: #23123

There are a bunch of other failures as well:

The following tests FAILED:
         39 - VSGNUFortran (Failed)
        121 - CustomCommand (Failed)
        135 - CPackComponentsForAll-RPM-IgnoreGroup (Failed)
        267 - Fortran (Failed)
        269 - FortranC.Flags (Failed)
        415 - RunCMake.PositionIndependentCode (Failed)
        542 - RunCMake.CPack_RPM.DEBUGINFO (Failed)
Errors while running CTest

I have not reproduced those under GCC 12 proper, so maybe they happen because “scl enable gcc-toolset-12 -- bash” results in some incompatibilities. Some of the failures are suppressed during the RPM build; I skipped that part.

(NB: gcc is not installed on this system.)

Comment 1 RHEL Program Management 2023-09-22 16:39:44 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-22 16:40:58 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Note You need to log in before you can comment on or make changes to this bug.