@@ -17,9 +17,8 @@ $(H2 $(LNAME2 fp_intermediate_values, Floating-Point Intermediate Values))
17
17
implemented by the hardware.
18
18
)
19
19
20
- $(P It's possible that, due to greater use of temporaries and
21
- common subexpressions, optimized code may produce a more
22
- accurate answer than unoptimized code.)
20
+ $(P Execution of floating-point expressions may yield a result of greater precision than dictated
21
+ by the source.)
23
22
24
23
$(H2 $(LNAME2 fp_const_folding, Floating-Point Constant Folding))
25
24
@@ -85,7 +84,7 @@ $(H2 $(LNAME2 rounding_control, Rounding Control))
85
84
)
86
85
87
86
88
- $(H2 $(LNAME2 esception_flags , Exception Flags))
87
+ $(H2 $(LNAME2 exception_flags , Exception Flags))
89
88
90
89
$(P IEEE 754 floating-point arithmetic can set several flags based on what
91
90
happened with a
@@ -105,14 +104,11 @@ $(H2 $(LNAME2 esception_flags, Exception Flags))
105
104
$(H2 $(LNAME2 floating-point-transformations, Floating-Point Transformations))
106
105
107
106
$(P An implementation may perform transformations on
108
- floating-point computations in order to reduce their strength,
109
- i.e. their runtime computation time.
110
- Because floating-point math does not precisely follow mathematical
111
- rules, some transformations are not valid, even though some
112
- other programming languages still allow them.
107
+ floating-point computations in order to reduce their strength.
113
108
)
114
109
115
- $(P The following transformations of floating-point expressions
110
+ $(P Not all transformations are valid: The following
111
+ transformations of floating-point expressions
116
112
are not allowed because under IEEE rules they could produce
117
113
different results.
118
114
)
0 commit comments