The encoding of operands and results in test vectors for decimal [equivalence] binary conversion logically differs from the encodings described previously.

To this format-independent generalization, which consisted of about 850 vectors, we then added approximately 650 precision-independent vectors for the conversion operators `r', `i', `ri', `ru', `rI', and `rU', and 14,500 precision dependent vectors to test decimal [equivalence] binary conversion (see Section 6 and Paxson and Kahan [1991]).

Whereas no test set for decimal [equivalence] binary conversion is included in Coonen [1984], tables of decimal numbers are available [Tydeman 1996] which require a lot more than 53 bits to achieve correct rounding to double-precision binary representation.

Both groups of test vectors also contain some cases where the decimal [equivalence] binary conversion is exact or induces either overflow or underflow.

ieee test decimal [equivalence] binary conversion only within range where IEEE requires exact rounding; this option can be abbreviated to -i

The same holds for the g++ compiler, except for decimal [equivalence] binary conversion which is only supported in round to nearest.

In this programming environment, besides some exception signaling errors, erroneous results are returned in decimal [equivalence] binary conversion.

In this programming environment, erroneous results again only occur in decimal [equivalence] binary conversion, which are the only conversions not implemented in hardware on x87 platforms.