Hi, I'm looking through the atlas code. In 2017, I did contribute changes to packaging to compile atlas with the ARCHS set to z12 on ubuntu (up from z9, and provided the matching archdefs).
Looking at the upstream code I do not see any z13 or z14 specific code in atlas - are there any? do we need to upgrade atlas? Is this a request to simply compile the library with `-march=zEC12 -mtune=z14` options? Ideally, we would want to avoid providing three builds for each of the -march=zEC12, -march=z13, -march=z14. Ideally, we would have a single `fat` binary that does runtime detection and does utilize the best available vectorization it can; with explicit code changes or by utilizing automatic compiler function multi- versioning. I.e. many other libraries on s390x and other architectures do runtime detection to exploit NEO, Altivec, AVX2, etc, rather than provide separate builds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803077 Title: libatlas not using vector instructions - large performance impact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1803077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
