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 1986987 - nss disables LTO in RHEL 9
Summary: nss disables LTO in RHEL 9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: nss
Version: 9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: beta
: ---
Assignee: Bob Relyea
QA Contact: Ivan Nikolchev
URL:
Whiteboard:
Depends On: 1986627
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-28 16:16 UTC by Bob Relyea
Modified: 2022-05-17 13:10 UTC (History)
9 users (show)

Fixed In Version: nss-3.71.0-6.el9
Doc Type: No Doc Update
Doc Text:
Clone Of: 1986627
Environment:
Last Closed: 2022-05-17 12:47:48 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CRYPTO-6092 0 None None None 2022-01-27 11:43:59 UTC
Red Hat Product Errata RHEA-2022:2398 0 None None None 2022-05-17 12:48:03 UTC

Description Bob Relyea 2021-07-28 16:16:52 UTC 
+++ This bug was initially created as a clone of Bug #1986627 +++

nss opted out of building with LTO in Fedora in 3.55.0-2:
  https://src.fedoraproject.org/rpms/nss/c/d4e86043ee0de880c84f0d6ce5267a5ce16c97ef
with the message:
  # This package fails its testsuite with LTO.  Disable LTO for now
and building it with LTO is currently still disabled in rawhide.

It would be good to either:
(a) enable LTO for nss in Fedora so that nss can benefit from LTO (smaller/faster machine code, deeper analysis for compiler warnings, etc), or
(b) capture what the problem was, in case something needs fixing in nss, or at the toolchain end.

Hence this bug.  What specific issues do you run into if you remove the
  %global _lto_cflags %{nil}
?  Is this being tracked in upstream nss or upstream gcc?  (and do you need help from the toolchain team on this?)

Thanks
Dave

--- Additional comment from Bob Relyea on 2021-07-27 17:08:02 PDT ---

It looks like Daiki turned if off last year. I'll have to see what the actual failure is. I'm currently running an nss rebuild to handle the mass rebuild issue.
Daiki's comments indicated that the nss upstream tests, which are run as part of the the nss build, fails with lto_cflags on.

Looks like there wasn't an upstream bug originally, bug umbutu has one now:
https://bugzilla.mozilla.org/show_bug.cgi?id=1721995

They had problems with s390.

When my current NSS build is complete, I'll do a scratch build to see which tests and platforms fail if I turn lto on.
Comment 6 errata-xmlrpc 2022-05-17 12:47:48 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: nss), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2022:2398
Note You need to log in before you can comment on or make changes to this bug.