x86-64 level
x86-64-v2
Vendor
AMD
First products
2012
Products
FX (for example FX-8350); A-Series (Trinity, Richland); Opteron 3300, 4300 and 6300
Segments
desktopmobileworkstationserverembedded
GCC target
-march=bdver2
Optimization
Optimizing code for Bulldozer to Excavator

Has FMA, F16C and BMI1 but not AVX2, BMI2 or MOVBE, so it stops at x86-64-v2.

Product lines

The product lines built on Piledriver, with the market segment the vendor sells each in and the sockets or soldered (BGA) packages its processors come in. Each socket links to the vendor page that states it.
Product lineSegmentSocketSource
FXdesktopAM3+ir.amd.com
A-Series (Trinity)desktopFM2ir.amd.com
A-Series (Trinity)mobileFS1r2, FP2 (BGA)ir.amd.com
A-Series (Richland)desktopFM2ir.amd.com
A-Series (Richland)mobileFS1r2, FP2 (BGA)ir.amd.com
Athlon X4desktopFM2amd.com
FirePro A300workstationFM2ir.amd.com
Opteron 3300serverAM3+ir.amd.com
Opteron 4300serverC32ir.amd.com
Opteron 6300serverG34ir.amd.com
R-SeriesembeddedFS1r2, FP2 (BGA)ir.amd.com

Why not x86-64-v3?

Piledriver lacks AVX2, BMI2 and MOVBE, all of which x86-64-v3 requires.

Feature checklist

Features required by each x86-64 level and whether Piledriver has them. OSFXSR and OSXSAVE are set by the operating system; the table checks the hardware features they depend on.
FeaturePiledriverEnumerated byLinux flag
x86-64-v1
CMOVYesCPUID.01H:EDX[15]cmov
CX8YesCPUID.01H:EDX[8]cx8
FPUYesCPUID.01H:EDX[0]fpu
FXSRYesCPUID.01H:EDX[24]fxsr
MMXYesCPUID.01H:EDX[23]mmx
OSFXSR via FXSRYesCPUID.01H:EDX[24]fxsr
SCEYesCPUID.80000001H:EDX[11]syscall
SSEYesCPUID.01H:EDX[25]sse
SSE2YesCPUID.01H:EDX[26]sse2
x86-64-v2
CMPXCHG16BYesCPUID.01H:ECX[13]cx16
LAHF-SAHFYesCPUID.80000001H:ECX[0]lahf_lm
POPCNTYesCPUID.01H:ECX[23]popcnt
SSE3YesCPUID.01H:ECX[0]pni
SSE4.1YesCPUID.01H:ECX[19]sse4_1
SSE4.2YesCPUID.01H:ECX[20]sse4_2
SSSE3YesCPUID.01H:ECX[9]ssse3
x86-64-v3
AVXYesCPUID.01H:ECX[28]avx
AVX2NoCPUID.(EAX=07H,ECX=0):EBX[5]avx2
BMI1YesCPUID.(EAX=07H,ECX=0):EBX[3]bmi1
BMI2NoCPUID.(EAX=07H,ECX=0):EBX[8]bmi2
F16CYesCPUID.01H:ECX[29]f16c
FMAYesCPUID.01H:ECX[12]fma
LZCNTYesCPUID.80000001H:ECX[5]abm
MOVBENoCPUID.01H:ECX[22]movbe
OSXSAVE via XSAVEYesCPUID.01H:ECX[26]xsave
x86-64-v4
AVX512FNoCPUID.(EAX=07H,ECX=0):EBX[16]avx512f
AVX512BWNoCPUID.(EAX=07H,ECX=0):EBX[30]avx512bw
AVX512CDNoCPUID.(EAX=07H,ECX=0):EBX[28]avx512cd
AVX512DQNoCPUID.(EAX=07H,ECX=0):EBX[17]avx512dq
AVX512VLNoCPUID.(EAX=07H,ECX=0):EBX[31]avx512vl

Other extensions

Notable extensions outside the x86-64 levels. Vendors sometimes disable these on individual models. Linked names lead to the extension's instructions.

Known vulnerabilities

The CVEs that the sources of the vulnerability list name as affecting Piledriver, in all of its models or in some of them.

Sources

  1. GCC -march=bdver2 feature set (PTA_BDVER2)
  2. Second-Generation AMD A-Series APUs Enable Best-in-Class PC Mobility, Entertainment, and Gaming Experience in Single Chip (AMD press release, May 15, 2012): The A-Series (Trinity) APUs, with Piledriver cores.
  3. AMD Reports 2012 Fourth Quarter and Annual Results (AMD press release, January 22, 2013): New FX processors such as the FX-8350, based on the Piledriver core.