Intel 253668-032US User Manual
Vol. 3 19-17
ARCHITECTURE COMPATIBILITY
19.18.7 Changes to Floating-Point Instructions
This section identifies the differences in floating-point instructions for the various
Intel FPU and math coprocessor architectures, the reason for the differences, and
their impact on software.
Intel FPU and math coprocessor architectures, the reason for the differences, and
their impact on software.
19.18.7.1 FDIV, FPREM, and FSQRT Instructions
The 32-bit x87 FPUs support operations on denormalized operands and, when
detected, an underflow exception can occur, for compatibility with the IEEE Standard
754. The 16-bit IA-32 math coprocessors do not operate on denormalized operands
or return underflow results. Instead, they generate an invalid-operation exception
when they detect an underflow condition. An existing underflow exception handler
will require change only if it gives different treatment to different opcodes. Also, it is
possible that fewer invalid-operation exceptions will occur.
detected, an underflow exception can occur, for compatibility with the IEEE Standard
754. The 16-bit IA-32 math coprocessors do not operate on denormalized operands
or return underflow results. Instead, they generate an invalid-operation exception
when they detect an underflow condition. An existing underflow exception handler
will require change only if it gives different treatment to different opcodes. Also, it is
possible that fewer invalid-operation exceptions will occur.
19.18.7.2 FSCALE Instruction
With the 32-bit x87 FPUs, the range of the scaling operand is not restricted. If (0 < |
ST(1) < 1), the scaling factor is 0; therefore, ST(0) remains unchanged. If the
rounded result is not exact or if there was a loss of accuracy (masked underflow), the
precision exception is signaled. With the 16-bit IA-32 math coprocessors, the range
of the scaling operand is restricted. If (0 < | ST(1) | < 1), the result is undefined and
no exception is signaled. The impact of this difference on exiting software is that
different results are delivered on the 32-bit and 16-bit FPUs and math coprocessors
when (0 < | ST(1) | < 1).
ST(1) < 1), the scaling factor is 0; therefore, ST(0) remains unchanged. If the
rounded result is not exact or if there was a loss of accuracy (masked underflow), the
precision exception is signaled. With the 16-bit IA-32 math coprocessors, the range
of the scaling operand is restricted. If (0 < | ST(1) | < 1), the result is undefined and
no exception is signaled. The impact of this difference on exiting software is that
different results are delivered on the 32-bit and 16-bit FPUs and math coprocessors
when (0 < | ST(1) | < 1).
19.18.7.3 FPREM1 Instruction
The 32-bit x87 FPUs compute a partial remainder according to IEEE Standard 754.
This instruction does not exist on the 16-bit IA-32 math coprocessors. The avail-
ability of the FPREM1 instruction has is no impact on existing software.
This instruction does not exist on the 16-bit IA-32 math coprocessors. The avail-
ability of the FPREM1 instruction has is no impact on existing software.
19.18.7.4 FPREM Instruction
On the 32-bit x87 FPUs, the condition code flags C0, C3, C1 in the status word
correctly reflect the three low-order bits of the quotient following execution of the
FPREM instruction. On the 16-bit IA-32 math coprocessors, the quotient bits are
incorrect when performing a reduction of (64
correctly reflect the three low-order bits of the quotient following execution of the
FPREM instruction. On the 16-bit IA-32 math coprocessors, the quotient bits are
incorrect when performing a reduction of (64
N
+ M) when (N ≥ 1) and M is 1 or 2. This
difference does not affect existing software; software that works around the bug
should not be affected.
should not be affected.
19.18.7.5 FUCOM, FUCOMP, and FUCOMPP Instructions
When executing the FUCOM, FUCOMP, and FUCOMPP instructions, the 32-bit x87
FPUs perform unordered compare according to IEEE Standard 754. These instruc-
FPUs perform unordered compare according to IEEE Standard 754. These instruc-