Extensions
Forms
1 (1 Legacy)
Data
Intel XED v2026.08.23

FDECSTP subtracts 1 from TOP, the 3-bit field of the x87 status word that says which physical register is ST(0); from 0 it wraps to 7. No register’s value or tag changes, so the register that was ST(7) becomes ST(0), with whatever it held, and the old ST(0) becomes ST(1). It is two bytes, D9 F6, and undoes FINCSTP.

Not a push

A push, as in FLD, also subtracts 1 from TOP, but then writes a value into the new ST(0) and tags it valid, and first checks that the register is empty. FDECSTP does neither. On Zen 5, FDECSTP on a stack of three values made an empty register ST(0), and the three values became ST(1) to ST(3). An instruction that reads ST(0) next finds a stack underflow, IE and SF with C1 = 0. FDECSTP followed by FINCSTP, or the other way round, leaves the stack as it was.

No exception of its own

FDECSTP raises no floating-point exception, whatever the tags: Zen 5 moved TOP from 7 to 6 with all eight registers empty, and from 3 to 2 with all eight full. Intel’s manual lists #MF for an unmasked exception pending before it, as for any waiting x87 instruction. Both manuals clear C1 and leave C0, C2 and C3 undefined; in all six of Zen 5’s cases FDECSTP cleared C1 and kept the other three.

AMD’s Zen 5 guide lists FDECSTP as one macro-op, six per cycle, with no FP pipe named.

Forms

Every encoding of FDECSTP that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
FDECSTP FDECSTPD9 F6FPU

Operation

What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.

top = top - 1                        # from 0 to 7
c1 = 0
c0 = c2 = c3 = UNDEFINED

Run on AMD Zen 5 (EPYC 9645): 6 cases.

Operands

What each form reads and writes, as Intel XED records it: the operands of its syntax, in order, and the implicit ones that the syntax does not name. How to read.
OperandKindAction
FDECSTP
x87 status wordimplicitread, write

Flags

M modified, U undefined; blank: not affected. How to read.
C0C1C2C3
All forms
UMUU

Attributes

What else XED records about the forms. How to read.

All forms
may abort a TSX transaction

CPUID and processors

Each form belongs to an XED ISA set. A form can be used when the processor reports every CPUID bit of one of its ISA set's alternatives.

CPUID requirements and processors of the XED ISA sets above. Alternatives are separated by “or”; processors follow XED’s chip model, whose AMD processors end with Zen 2, and the CPU data of this site for Zen 3 to Zen 6.
ISA setCPUIDProcessors
X87

FPU
CPUID.01H:EDX[0] FPU

Every x86-64 processor in XED’s model and Zen 3 to Zen 6

More x87 instructions

All 90 x87 instructions

Sources

  1. Intel XED v2026.08.23 (commit 0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model.
  2. The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s -march feature sets and AMD’s Processor Programming References, which the page of each processor cites.
  3. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2A, page 3-332 (FDECSTP)
  4. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  5. AMD64 Architecture Programmer's Manual, Volume 5: 64-Bit Media and x87 Floating-Point Instructions (26569, rev. 3.16, November 2021), Wayback Machine copy of AMD's PDF
  6. Software Optimization Guide for the AMD Zen5 Microarchitecture (58455, rev. 1.00, August 2024), Wayback Machine copy of AMD's ZIP

The tables are derived from Intel XED, Copyright Intel Corporation, licensed under the Apache License 2.0; x86-64.net converted and reformatted them. The text is our own.