[Bug 1951032] Re: AArch64: Backport memcpy improvements

[Michael Hudson-Doyle]

** Description changed:

  [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]
- TBD.
+ The testcase from https://bugs.launchpad.net/ubuntu/focal/+source/glibc/+bug/1928508 can be used for this too.
  
  [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.

-- 
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:
  New

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]
  The testcase from https://bugs.launchpad.net/ubuntu/focal/+source/glibc/+bug/1928508 can be used for this too.

  [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