Bug 1652928 - glibc needs to be rebuild on ppc64le for new str[n]cmp inlined code
Summary: glibc needs to be rebuild on ppc64le for new str[n]cmp inlined code
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Carlos O'Donell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1652927
Blocks: 1652926
TreeView+ depends on / blocked
 
Reported: 2018-11-23 15:32 UTC by Mark Wielaard
Modified: 2019-10-01 13:51 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-01 13:51:38 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.