df@ or df! used with an address that is not double-float aligned: ¶Hardware-dependent. If the hardware does not support unaligned
accesses, this typically results in a -23 THROW like other
alignment violations.
f@ or f! used with an address that is not float aligned: ¶Hardware-dependent. If the hardware does not support unaligned
accesses, this typically results in a -23 THROW like other
alignment violations.
An FP value is returned (so nothing is out of range), but it may be an infinity or a NaN.
sf@ or sf! used with an address that is not single-float aligned: ¶Hardware-dependent. If the hardware does not support unaligned
accesses, this typically results in a -23 THROW like other
alignment violations.
base is not decimal (REPRESENT, F., FE., FS.): ¶Conversion between FP and string representations always use decimal,
irrespective of base.
FATAN2): ¶System-dependent. FATAN2 is implemented using the C library
function atan2().
FTAN on an argument r1 where cos(r1) is zero: ¶System-dependent. Anyway, typically the cos of r1 will not be zero because of small errors and the tan will be a very large (or very small) but finite number.
D>F: ¶The result is rounded to the nearest float.
On IEEE FP based systems, prouces an infinity or a NaN.
DF!, DF@, SF!, SF@): ¶On IEEE-FP based systems the number is converted into an infinity.
FACOSH): ¶On IEEE-FP based systems this produces a NaN.
FLNP1): ¶On IEEE-FP based systems this produces a NaN (or a negative infinity for float=-1).
FLN, FLOG): ¶On IEEE-FP based systems this produces a NaN (or a negative infinity for float=0).
FASINH, FSQRT): ¶On IEEE-FP based systems, for fsqrt this gives a NaN, for
fasinh some platforms produce a NaN, others a number.
FACOS, FASIN, FATANH): ¶IEEE-FP based systems produce a NaN.
F>D: ¶Platform-dependent; typically, some double number is produced and no error is reported.
f., fe., fs.): ¶These words do not use the pictured numeric output buffer, but a buffer big enough for the needs of these words.