Bug 1708309

Summary:	gcc: Linking against libgcc_s should imply linking with libgcc
Product:	Red Hat Enterprise Linux 8	Reporter:	Marek Polacek <mpolacek>
Component:	gcc	Assignee:	Marek Polacek <mpolacek>
gcc sub component:	system-version	QA Contact:	Alexandra Petlanová Hájková <ahajkova>
Status:	CLOSED ERRATA	Docs Contact:	Vladimír Slávik <vslavik>
Severity:	unspecified
Priority:	unspecified	CC:	ahajkova, fweimer, jakub, law, mcermak, mpetlan, ohudlick
Version:	8.1
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gcc-8.3.1-4.2.el8	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 22:16:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1684553

Description Marek Polacek 2019-05-09 14:59:58 UTC

Same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1688766.  We'll need to apply this:
https://src.fedoraproject.org/rpms/gcc/c/62b413d244caaf088f1d4a73b30a9e3b0ad4cbef?branch=f29

Comment 5 Alexandra Petlanová Hájková 2019-07-30 12:06:48 UTC

I verified g++ does not link against libgcc.a for gcc-8.3.1-4.1:
g++ -O2 -fpic -shared reproducer.c
eu-readelf -s a.out | grep cpu_model
3: 0000000000000000      0 NOTYPE  GLOBAL DEFAULT    UNDEF __cpu_model
50: 0000000000000000      0 NOTYPE  GLOBAL DEFAULT    UNDEF __cpu_model

and g++ links against libgcc.a for gcc-8.3.1-4.2.el8:
++ -O2 -fpic -shared reproducer.c
eu-readelf -s a.out | grep cpu_model
50: 0000000000202030     16 OBJECT  LOCAL  DEFAULT       22 __cpu_model

Comment 7 errata-xmlrpc 2019-11-05 22:16:40 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://access.redhat.com/errata/RHBA-2019:3565