[Bug 1951032] Re: AArch64: Backport memcpy improvements
Steve Langasek
1951032 at bugs.launchpad.net
Mon Dec 13 06:03:54 UTC 2021
Hello Michael, or anyone else affected,
Accepted glibc into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: glibc (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1951032
Title:
AArch64: Backport memcpy improvements
Status in glibc package in Ubuntu:
Invalid
Status in glibc source package in Focal:
Fix Committed
Bug description:
[impact]
glibc 2.32 contained a number of improvements to the memcpy routines for server-grade AArch64 implementations (in particular, graviton2 & graviton3). They should be backported to focal, as the LTS releases are by far the most used on servers.
[test case]
Compile the test_memcpy.c that is attached to bug 1928508:
$ gcc -g -O3 test_memcpy.c -o test_memcpy64
This should be run before and after installing the libc packages from
proposed. On graviton2 systems, this should show a substantial
improvement. On other arm64 systems (raspberry pis of various vintage,
thunderx2, xgene, etc etc) at least no significant regression should
be seen.
[regression potential]
Rebuilding glibc is always a little risky (toolchain bugs and incompatibilities between the old and new versions can be surprising). But the autopkgtests and some manual general testing can help here.
For this specific change, there is a potential risk that the new
memcpy implementation could be used on a system where it is not in
fact the fastest. We should run the test case not only on the systems
where it is expected to help, but other systems such as the RPi4 and
the launchpad build farm to ensure performance is not regressed there.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1951032/+subscriptions
More information about the foundations-bugs
mailing list