x86-64-v3
Notes
- Specifying
-march=x86-64-v3
implies-mtune=generic
, check with:
-
isl
andlibffi
use-with-gcc-arch
which specifies the passed value tomarch
only (and does not pass it tomtune
) which is needed to prevent the configure script from guessing the wrong architecture (it detects the native architecture e.g.haswell
oramdfam10
instead) -
Output when passing
-with-gcc-arch=x86-64-v3
toisl
andlibffi
- To verify if the build was successful, try with
qemu
, when targetingx86-64-v3
regularqemu
will not work without passingcpu
beinghost
Resources
- https://fedoraproject.org/wiki/Changes/Optimized_Binaries_for_the_AMD64_Architecture
- https://www.phoronix.com/news/openSUSE-Tumbleweed-x86-64-v2
- https://sunnyflunk.github.io/2023/01/15/x86-64-v3-Mixed-Bag-of-Performance.html
- https://discourse.nixos.org/t/pre-rfc-gradual-transition-of-nixos-x86-64-baseline-to-x86-64-v3-with-an-intermediate-step-to-x86-64-v2/35924
- https://github.com/NixOS/nixpkgs/pull/202526
- https://github.com/NixOS/nixpkgs/issues/63708
- https://www.gentoo.org/news/2024/02/04/x86-64-v3.html
- https://github.com/glaucuslinux/rad/commit/4d978149e5c82ee7d5f4370c97e88e79eb644fd3