Bug 1652928

Summary:	glibc needs to be rebuild on ppc64le for new str[n]cmp inlined code
Product:	[Fedora] Fedora	Reporter:	Mark Wielaard <mjw>
Component:	glibc	Assignee:	Carlos O'Donell <codonell>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	29	CC:	arjun, codonell, dj, fweimer, law, mfabian, pfrankli, rth, siddhesh
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-01 13:51:38 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:	1652927
Bug Blocks:	1652926

Description Mark Wielaard 2018-11-23 15:32:25 UTC

On ppc64le gcc8 generates inlined code for str[n]cmp that valgrind memcheck
cannot proof correct. gcc9/trunk generates slightly different code for the
inlined strncmp code that valgrind memcheck can proof correct with some
patches. glibc uses inlined str[n]cmp in various functions.

Once the gcc patch has been backported (#1652927) glibc should be rebuild with the new gcc to solve the valgrind bug (#1652926).

Comment 1 Mark Wielaard 2018-12-20 21:42:55 UTC

gcc-8.2.1-6 has landed in f28 and f29.
valgrind-3.14.0-7 has been pushed to fedora 28 and fedora 29 testing.
It would be great if glibc could be rebuild against the new gcc now for f28 and f29.