2–24
Internal Architecture
29 September 1997 – Subject To Change
Scheduling and Issuing Rules
Table 2–9 Instruction Latencies
(Sheet 1 of 2)
Class
Latency
Additional Time Before
Result Available to
Integer Multiply Unit
1
LD
Dcache hits, latency=2.
Dcache miss/Bcache hit, latency=10 or longer.
2
1 cycle
ST
Store operations produce no result.
—
MBX
LDx_L Dcache hits, latency=2.
LDx_L Dcache miss/Bcache hit, latency=10 or longer.
LDx_L Dcache miss/Bcache miss, latency depends on memory
subsystem state.
STx_C, latency depends on memory subsystem state.
MB, WMB, and FETCH produce no result.
—
RX
RS, RC, latency=1.
2 cycles
MXPR
HW_MFPR, latency=1, 2, or longer, depending on the IPR.
HW_MTPR, produces no result.
1 or 2 cycles
IBR
Produces no result. (Taken branch issue latency minimum=1
cycle, branch mispredict penalty=5 cycles.)
—
FBR
Produces no result. (Taken branch issue latency minimum=1
cycle, branch mispredict penalty=5 cycles.)
—
JSR
All but HW_REI, latency=1.
HW_REI produces no result. (Issue latency—minimum 1 cycle.)
2 cycles
SEXT
Latency=1.
2 cycles
IADD
Latency=1.
2 cycles
ILOG
Latency=1.
3
2 cycles
SHIFT
Latency=1.
2 cycles
CMOV
Latency=2.
1 cycle
ICMP
Latency=1.
2 cycles
IMULL Latency=8, plus up to 2 cycles of added latency, depending on the
source of the data.
Latency until next IMULL, IMULQ, or
IMULH instruction can issue (if there are no data dependencies) is
4 cycles plus the number of cycles added to the latency.
1 cycle