Intel E6600 Specification Update - Page 29

AI19., Code Segment Limit Violation May Occur on 4 Gigabyte Limit Check, AI20.

Page 29 highlights

Errata ordering issue if multiple loads access this shared data shortly thereafter. Exposure to this problem requires the use of a data write which spans a cache line boundary. Implication: This erratum may cause loads to be observed out of order. Intel has not observed this erratum with any commercially available software or system. Workaround: Software should ensure at least one of the following is true when modifying shared data by multiple agents: • The shared data is aligned • Proper semaphores or barriers are used in order to prevent concurrent data accesses. Status: For the steppings affected, see the Summary Tables of Changes. AI19. Code Segment Limit Violation May Occur on 4 Gigabyte Limit Check Problem: Code Segment limit violation may occur on 4 Gigabyte limit check when the code stream wraps around in a way that one instruction ends at the last byte of the segment and the next instruction begins at 0x0. Implication: This is a rare condition that may result in a system hang. Intel has not observed this erratum with any commercially available software, or system. Workaround: Avoid code that wraps around segment limit. Status: For the steppings affected, see the Summary Tables of Changes. AI20. Problem: FP Inexact-Result Exception Flag May Not Be Set When the result of a floating-point operation is not exactly representable in the destination format (1/3 in binary form, for example), an inexact-result (precision) exception occurs. When this occurs, the PE bit (bit 5 of the FPU status word) is normally set by the processor. Under certain rare conditions, this bit may not be set when this rounding occurs. However, other actions taken by the processor (invoking the software exception handler if the exception is unmasked) are not affected. This erratum can only occur if one of the following FST instructions is one or two instructions after the floatingpoint operation which causes the precision exception: • FST m32real • FST m64real • FSTP m32real • FSTP m64real • FSTP m80real • FIST m16int • FIST m32int • FISTP m16int • FISTP m32int • FISTP m64int • FISTTP m16int • FISTTP m32int • FISTTP m64int Intel® Core™2 Extreme Processor X6800 and Intel® Core™2 Duo Desktop Processor E6000 and E4000 Sequence 29 Specification Update

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71

Errata
Intel
®
Core™2 Extreme Processor X6800 and
Intel
®
Core™2 Duo Desktop Processor E6000 and E4000 Sequence
29
Specification Update
ordering issue if multiple loads access this shared data shortly thereafter.
Exposure to this problem requires the use of a data write which spans a
cache line boundary.
Implication:
This erratum may cause loads to be observed out of order. Intel has not
observed this erratum with any commercially available software or system.
Workaround:
Software should ensure at least one of the following is true when modifying
shared data by multiple agents:
The shared data is aligned
Proper semaphores or barriers are used in order to prevent concurrent data
accesses.
Status:
For the steppings affected, see the Summary Tables of Changes.
AI19.
Code Segment Limit Violation May Occur on 4 Gigabyte Limit Check
Problem:
Code Segment limit violation may occur on 4 Gigabyte limit check when the
code stream wraps around in a way that one instruction ends at the last byte
of the segment and the next instruction begins at 0x0.
Implication:
This is a rare condition that may result in a system hang. Intel has not
observed this erratum with any commercially available software, or system.
Workaround:
Avoid code that wraps around segment limit.
Status:
For the steppings affected, see the Summary Tables of Changes.
AI20.
FP Inexact-Result Exception Flag May Not Be Set
Problem:
When the result of a floating-point operation is not exactly representable in
the destination format (1/3 in binary form, for example), an inexact-result
(precision) exception occurs. When this occurs, the PE bit (bit 5 of the FPU
status word) is normally set by the processor. Under certain rare conditions,
this bit may not be set when this rounding occurs. However, other actions
taken by the processor (invoking the software exception handler if the
exception is unmasked) are not affected. This erratum can only occur if one
of the following FST instructions is one or two instructions after the floating-
point operation which causes the precision exception:
FST m32real
FST m64real
FSTP m32real
FSTP m64real
FSTP m80real
FIST m16int
FIST m32int
FISTP m16int
FISTP m32int
FISTP m64int
FISTTP m16int
FISTTP m32int
FISTTP m64int