Description of problem: Arm V8.5 CPUs are expected in the RHEL 9 timeframe, as such Glibc on aarch64 should be built with --enable-memory-tagging. A similar defect for fedora is here: 1944758 There is another more general (kernel focused) RHEL 9 defect: 1894743 Version-Release number of selected component (if applicable): 2.33-2
I assume this is just a simple spec file change, like this: + %ifarch aarch64 + --enable-memory-tagging \ + %endif Can we do this for glibc 2.33, or should we wait until the rebase to glibc 2.34? Thanks.
(In reply to Florian Weimer from comment #2) > I assume this is just a simple spec file change, like this: > > + %ifarch aarch64 > + --enable-memory-tagging \ > + %endif > > Can we do this for glibc 2.33, or should we wait until the rebase to glibc > 2.34? Thanks. We received feedback from Arm about this. The answer to this is as follows: - The 2.33 release has everything that we need to enable memory tagging and small fixes were backported into the release branch. - That 2.34 has only performance improvements. Therefore we can move this forward with glibc 2.33.