Beneath adding the platform name, the glibc-hwcaps subdirectories feature is extended. The z16 subfolder is now also searched for "z16" specific libraries if support is indicated by the HWCAPs.
[Test Plan]
Testing of the glibc-hwcaps feature is done by tst-glibc-hwcaps.c test from glibc-testsuite. In short: Different shared libraries are placed in the z16/z15/... subdirectories. A runtime-check tests whether the correct library was loaded on the particular machine.
Yes, IBM will test this feature on a z16 as soon as the libc packages are updated.
[Where problems could occur]
The mentioned patch does only change s390. Other architectures are not involved.
------- Comment From <email address hidden> 2022-07-05 04:17 EDT-------
[Impact]
The first part of z16 support went into glibc-2.34: /sourceware. org/git/ ?p=glibc. git;a=commit; h=25251c0707fe3 4f30a27381a5fab c35435a96621
- glibc commit "S390: Add new hwcap values."
https:/
After IBM z16 has been announced, we need to add the new s390 platform in glibc: /sourceware. org/git/ ?p=glibc. git;a=commit; h=2376944b9e5c0 364b9fb473e4d8d abca31b57167 /sourceware. org/git/ ?p=glibc. git;a=commit; h=6583d534458e7 f8beec8d0766b6d b0bdaae6749c
- glibc upstream commit "S390: Add new s390 platform z16."
https:/
- Backport to glibc 2.35 release branch:
https:/
Beneath adding the platform name, the glibc-hwcaps subdirectories feature is extended. The z16 subfolder is now also searched for "z16" specific libraries if support is indicated by the HWCAPs.
[Test Plan]
Testing of the glibc-hwcaps feature is done by tst-glibc-hwcaps.c test from glibc-testsuite. In short: Different shared libraries are placed in the z16/z15/... subdirectories. A runtime-check tests whether the correct library was loaded on the particular machine.
Yes, IBM will test this feature on a z16 as soon as the libc packages are updated.
[Where problems could occur]
The mentioned patch does only change s390. Other architectures are not involved.