Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1937698 - gcc: Remove libstdc++ symbols which are not going to be part of the GCC 11 upstream release
Summary: gcc: Remove libstdc++ symbols which are not going to be part of the GCC 11 up...
Keywords:
Status: ASSIGNED
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 34
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jonathan Wakely
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1959316 1959320 1926594 1959307 1959310 1959312 1959319 1959323
Blocks: 1937700
TreeView+ depends on / blocked
 
Reported: 2021-03-11 11:17 UTC by Florian Weimer
Modified: 2021-05-11 09:35 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1937700 (view as bug list)
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Florian Weimer 2021-03-11 11:17:36 UTC 
The following symbols will be removed from libstdc++.so.6 before the GCC 11 upstream release:

_ZNSt9once_flag11_M_activateEv
_ZNSt9once_flag9_M_finishEb

We need to make this change in Fedora as well (in stages; first avoid creating symbol references from new builds, rebuild packages, and then remove the symbol for real).
Comment 1 Nicolas Chauvet (kwizart) 2021-04-02 16:28:06 UTC 
What is the best way to detect the usage of theses symbols in any (non-fedora) package ? rpm2cpio + readelf ?
Eventually, having the range of the affected gcc compiler would help (or the first known good compiler) ?


Thanks in advance.
Comment 2 Jonathan Wakely 2021-04-03 14:46:42 UTC 
(In reply to Nicolas Chauvet (kwizart) from comment #1)
> What is the best way to detect the usage of theses symbols in any
> (non-fedora) package ? rpm2cpio + readelf ?

Yes, that works.

> Eventually, having the range of the affected gcc compiler would help (or the
> first known good compiler) ?

The broken std::call_once was committed upstream Nov 3 2020. Rawhide switched to gcc-11.0.0 in late November, so all versions of gcc-11.0.0 will create references to the broken symbols. The fixed gcc that doesn't create references to those symbols (but still has them in libstdc++.so for now) is gcc-11.0.1-0.2.fc34 / gcc-11.0.1-0.2.fc35 (but the earlier build, gcc-11.0.1-0.1, is still bad).
Note You need to log in before you can comment on or make changes to this bug.