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 1164575 - -flto inlining bug
Summary: -flto inlining bug
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gcc
Version: 7.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jakub Jelinek
QA Contact: Miroslav Franc
URL:
Whiteboard:
Depends On:
Blocks: 1110700 1191021
TreeView+ depends on / blocked
 
Reported: 2014-11-16 16:40 UTC by Alex/AT
Modified: 2016-02-01 02:30 UTC (History)
7 users (show)

Fixed In Version: gcc-4.8.5-3.el7
Doc Type: Bug Fix
Doc Text:
No description necessary
Clone Of:
Environment:
Last Closed: 2015-11-19 12:22:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
PHP 5.5 spec with -flto option that is failing (1.33 KB, application/zip)
2015-06-11 20:07 UTC, Alex/AT
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNU Compiler Collection 59626 0 None None None Never
Red Hat Product Errata RHBA-2015:2080 0 normal SHIPPED_LIVE gcc bug fix and enhancement update 2015-11-19 10:51:58 UTC

Description Alex/AT 2014-11-16 16:40:28 UTC
To reproduce, i.e. try to compile php 5.5 with -flto. Gives:

/usr/include/bits/unistd.h:34:1: error: inlining failed in call to always_inline 'read': recursive inlining
 read (int __fd, void *__buf, size_t __nbytes)

A known bug. More details here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59626

Please include the fix into the GCC update.

Comment 5 Jakub Jelinek 2015-06-11 08:15:34 UTC
Richard Biener attached a backport to the upstream PR.  I'd like to make sure it fixes this bug, but To reproduce, i.e. try to compile php 5.5 with -flto. Gives:
is too vague.  Do you e.g. have a src.rpm that fails to build with RHEL 7.1 gcc that I could try with the unpatched and patched compiler?  Or just detailed instructions on what exactly you do to trigger it?

Comment 6 Alex/AT 2015-06-11 20:07:08 UTC
Created attachment 1037810 [details]
PHP 5.5 spec with -flto option that is failing

Comment 7 Alex/AT 2015-06-11 20:08:13 UTC
I have attached .spec that is failing. It requires nothing except php 5.5.20 source and its compile dependencies (not exactly written in .spec). If you don't have some deps, just disable them in configure options, it will fail nevertheless.

Comment 8 Alex/AT 2015-06-11 20:09:09 UTC
Or just do CFLAGS="-flto" CXXFLAGS="-flto" ./configure ; make on php 5.5

Comment 9 Alex/AT 2015-06-11 20:10:59 UTC
By the way, can I have the patch so I can rebuild gcc and test some more RPMs?

Comment 17 errata-xmlrpc 2015-11-19 12:22:05 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, 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://rhn.redhat.com/errata/RHBA-2015-2080.html


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