Comment 3 for bug 1799397

In the upstream discussion my confusion was resolved, this is in fact no issue of the binaries we generate.
It only happens if you rebuild it yourself with AVX512f enabled.
I'll participate and track the upstream discussion in case we can help fixing the code anyway - but by the provided binaries being ok this is much lower severity than I initially thought.