Comment # 5 on bug 1219031 from Richard Biener

Indeed, for example for cross-aarch64-gcc13 you'd get

> rpm -qp --provides /abuild/osc-build-root/.build.packages/RPMS/x86_64/cross-aarch64-gcc13-13.2.1+git8205-0.x86_64.rpm 
aarch64-suse-linux-gcc
cross-aarch64-gcc13 = 13.2.1+git8205-0
cross-aarch64-gcc13(x86-64) = 13.2.1+git8205-0
libatomic.so.1()(64bit)
libatomic.so.1(LIBATOMIC_1.0)(64bit)
libatomic.so.1(LIBATOMIC_1.1)(64bit)
libatomic.so.1(LIBATOMIC_1.2)(64bit)
libgcc_s.so.1()(64bit)
libgcc_s.so.1(GCC_11.0)(64bit)
libgcc_s.so.1(GCC_13.0.0)(64bit)
libgcc_s.so.1(GCC_3.0)(64bit)
libgcc_s.so.1(GCC_3.3)(64bit)
libgcc_s.so.1(GCC_3.3.1)(64bit)
libgcc_s.so.1(GCC_3.4)(64bit)
libgcc_s.so.1(GCC_3.4.2)(64bit)
libgcc_s.so.1(GCC_3.4.4)(64bit)
libgcc_s.so.1(GCC_4.0.0)(64bit)
...

that's of course wrong - it provides only aarch64 shared libraries, those
shouldn't be used for x86_64 provides.  It's similar for requires though
you'd see that mostly for a 32bit cross arch where it would wreck things.

So it's still a bad idea to turn AutoReqProv on when the package contains
non-native architecture executables or shared libraries.

In theory it could be possible to split the cross-* packages into parts
with only native objects and a 'noarch' -data sub-package to try to
workaround this issue.