x86-64-v3
x86-64-v3 is a cumulative psABI feature level adding AVX-era capabilities to x86-64-v2. The corresponding vector state must be enabled by the operating system, not merely present in the CPU.
What you need to know
x86-64-v3 is a cumulative psABI feature level adding AVX-era capabilities to x86-64-v2. The corresponding vector state must be enabled by the operating system, not merely present in the CPU.
How it works
Beyond v2, the level adds AVX, AVX2, BMI1, BMI2, F16C, FMA, LZCNT, MOVBE and OSXSAVE. The psABI requires the full processor-manual availability checks, including the relevant XCR0 state. This is a conjunction of requirements rather than a nickname for AVX2.
Where it is useful
A binary compiled with an x86-64-v3 target can use the whole level unconditionally. A broadly distributed library may instead keep a baseline build and select a v3 implementation through its loader or runtime dispatcher.
How to check support and enablement
Check every inherited and newly added feature and verify AVX OS-state enablement with the architecture's OSXSAVE/XGETBV sequence. Do not attempt to repair a missing hardware instruction by changing a software package label.
A hardware capability, the running operating environment and an application's binary requirements are different layers. Architecture names and ABI levels should be interpreted as explicit contracts rather than as a general newer-is-compatible rule.
What the feature does not establish
AVX2 alone does not establish v3, and v3 does not imply AES-NI, AVX-512 or AMX. A container shares the host kernel's instruction environment; it does not manufacture missing instructions. A VM may expose a compatible subset for migration.
Compatibility and performance in practice
Check the complete inherited requirements and the effective environment visible to the process. For a VM, inspect the guest rather than assuming the host model is exposed unchanged. A supported fallback build should state its own baseline clearly.
A practical verification checklist
- Record the exact processor or platform model and the application, OS and runtime versions involved. Preserve the wording of the actual error or requirement.
- Check the manufacturer reference for that exact model, then inspect the effective capability and enabled state in the environment where the program runs.
- Compare every requirement of the selected binary or backend. A similarly named feature, alias or broad technology label is not enough.
- Confirm the application selected the intended implementation. Use its documented diagnostics and a supported fallback when requirements are not met.
- Make one supported change at a time and repeat the same workload. Keep the original configuration and recovery path available.
If the feature is listed but software cannot use it
Start with the exact failing component. A hardware database describes recorded capability; the operating system or hypervisor can expose a different effective environment. An illegal-instruction error also needs investigation of the actual faulting instruction and binary build, because corruption or an unrelated unsupported instruction can produce a similar symptom.
Install the application, driver or runtime version supported for the exact platform, and use the vendor's documented baseline or fallback build if needed. A software update cannot create an instruction that the processor lacks. Firmware and security-policy changes should follow the system manufacturer's procedure and a recovery plan rather than a generic optimization recipe.
Sources and scope of this explanation
x86-64 psABI: processor architecture and microarchitecture levels · Intel 64 and IA-32 Architectures Software Developer's Manual · Linux kernel: using XSTATE features in user space
These references establish architectural behavior and software requirements. They do not independently verify every feature value on a linked hardware model page. For model support, use that page's manufacturer evidence and check the effective system configuration. This article does not supply a benchmark, certification or independent review date.
Sources and verification
Editorial ownership: Feex. No independent review date is recorded. How we research.
- x86-64 psABI: processor architecture and microarchitecture levels · Machine Interface, Processor Architecture: baseline and cumulative v2/v3/v4 feature table, OS-state checks and deployment recommendations.
- Intel 64 and IA-32 Architectures Software Developer's Manual · Volumes 1 and 2 describe the named instruction families and CPUID; Volume 3 describes state, paging, VMX and protection controls. Architecture documentation does not establish support for a particular model.
- Linux kernel: using XSTATE features in user space · OS-enabled vector state, dynamically enabled tile state, signal-stack requirements and AMX permission flow. Linux-specific behavior is not a promise about another OS.
Was this article useful?
A yes or no is enough. Pick a reason if you want, or add a short note.
Thanks. That helps us improve this page.