M68060 USER’S MANUAL
184.108.40.206 ACCRUED EXCEPTION BYTE.
The AEXC byte contains five exception bits (see
Figure 6-7) that the IEEE 754 standard requires for exception-disabled operations. These
exceptions are logical combinations of the bits in the EXC byte. The AEXC byte contains the
history of all floating-point exceptions that have occurred since the user last cleared the
AEXC byte. In normal operations, only the user clears this byte by writing to the FPSR; how-
ever, a reset or a restore operation of the null state can also clear the AEXC byte.
Many users elect to disable traps for all or part of the floating-point exception classes. The
AEXC byte makes it unnecessary to poll the EXC byte after each floating-point instruction.
At the end of most operations (FMOVEM and FMOVE excluded), the bits in the EXC byte
are logically combined to form an AEXC value that is logically ORed into the existing AEXC
byte. This operation creates sticky floating-point exception bits in the AEXC byte that the
user needs to poll only once (i.e., at the end of a series of floating-point operations). A sticky
bit is one that remains set until the user clears it.
Setting or clearing the AEXC bits neither causes nor prevents an exception. The following
equations show the comparative relationship between the EXC byte and AEXC byte. Com-
paring the current value in the AEXC bit with a combination of bits in the EXC byte derives
a new value in the corresponding AEXC bit. These equations apply to setting the AEXC bits
at the end of each operation affecting the AEXC byte:
Figure 6-6. Floating-Point Exception Status Byte (FPSR)
Figure 6-7. Floating-Point Accrued Exception Byte (FPSR)
SNAN OPERR OVFL UNFL DZ INEX2 INEX1
15 14 13 12 11 10 9 8
IOP OVFL UNFL DZ INEX
7 65432 0