
3:158
Volume 3: Instruction Reference
ldf
For more details on speculative, advanced and check loads see
and
Section 4.4.5, “Data Speculation” on page 1:63
on memory attributes are described in
Section 4.4, “Memory Attributes” on page 2:75
.
For the non-speculative load types, if NaT bit associated with GR
r
3
is 1, a Register NaT
Consumption fault is taken. For speculative and speculative advanced loads, no fault is
raised, and the exception is deferred. For the base-update calculation, if the NaT bit
associated with GR
r
2
is 1, the NaT bit associated with GR
r
3
is set to 1 and no fault is
raised.
The value of the
ldhint
modifier specifies the locality of the memory access. The
mnemonic values of
ldhint
are given in
. A prefetch hint is
implied in the base update forms. The address specified by the value in GR
r
3
after the
base update acts as a hint to prefetch the indicated cache line. This prefetch uses the
locality hints specified by
ldhint
. Prefetch and locality hints do not affect program
functionality and may be ignored by the implementation. See
Hierarchy Control and Consistency” on page 1:69
for details.
In the no_base_update form, the value in GR
r
3
is not modified and no prefetch hint is
implied.
The PSR.mfl and PSR.mfh bits are updated to reflect the modification of FR
f
1
.
Hardware support for
ldfe
(10-byte) instructions that reference a page that is neither a
cacheable page with write-back policy nor a NaTPage is optional. On processor models
that do not support such
ldfe
accesses, an Unsupported Data Reference fault is raised
when an unsupported reference is attempted. The fault is delivered only on the normal,
advanced, and check load flavors. Control-speculative flavors of
ldfe
always defer the
Unsupported Data Reference fault.
sa
Speculative
Advanced load
An entry is added to the ALAT, and certain exceptions may be deferred.
Deferral causes NaTVal to be placed in the target register, and the
processor ensures that no ALAT entry exists for the target register. The
absence of an ALAT entry is later used to detect deferral or collision.
c.nc
Check load –
no clear
The ALAT is searched for a matching entry. If found, no load is done
and the target register is unchanged. Regardless of ALAT hit or miss,
base register updates are performed, if specified. An implementation
may optionally cause the ALAT lookup to fail independent of whether an
ALAT entry matches. If not found, a load is performed, and an entry is
added to the ALAT (unless the referenced data page has a
non-speculative attribute, in which case no ALAT entry is allocated).
c.clr
Check load – clear
The ALAT is searched for a matching entry. If found, the entry is
removed, no load is done and the target register is unchanged.
Regardless of ALAT hit or miss, base register updates are performed, if
specified. An implementation may optionally cause the ALAT lookup to
fail independent of whether an ALAT entry matches. If not found, a clear
check load behaves like a normal load.
Table 2-36.
FP Load Types (Continued)
fldtype
Completer
Interpretation
Special Load Operation
Содержание Itanium 9150M
Страница 1: ......
Страница 209: ...3 200 Volume 3 Instruction Reference padd Interruptions Illegal Operation fault...
Страница 301: ...3 292 Volume 3 Pseudo Code Functions Intel Itanium Architecture Software Developer s Manual Rev 2 3...
Страница 405: ...3 396 Volume 3 Resource and Dependency Semantics...
Страница 406: ...3 397 Intel Itanium Architecture Software Developer s Manual Rev 2 3 Index...
Страница 407: ...3 398 Intel Itanium Architecture Software Developer s Manual Rev 2 3...
Страница 419: ...INDEX Index 12 Index for Volumes 1 2 3 and 4...
Страница 420: ......