Intel BCD opcodes

(Redirected from Intel BCD opcode)

The Intel BCD opcodes are a set of six x86 instructions that operate with binary-coded decimal numbers. The radix used for the representation of numbers in the x86 processors is 2. This is called a binary numeral system. However, the x86 processors do have limited support for the decimal numeral system.

In addition, the x87 part supports a unique 18-digit (ten-byte) BCD format that can be loaded into and stored from the floating point registers, from where ordinary FP computations can be performed.[1]

The integer BCD instructions are no longer supported in long mode.

Usage

edit

Number representation

edit

BCD numbers can be represented in two ways in integer registers: packed decimal and unpacked decimal.

  • Packed (4 bits)
    • In packed decimal representation a decimal digit is stored in one nibble.
    • The values 10 to 15 are not used.[2]
  • Unpacked (8 bits)
    • In unpacked decimal representation a decimal digit is stored in one byte.
    • The values 10 to 255 are not used.
    • The upper nibble is ignored, and can either be zero, or the leading-nibble for the ASCII character (value 3).[2]

BCD numbers are generally assumed to be stored in the lowest byte of a register, e.g. AL; operations on unpacked BCD numbers expect the least significant digit in the lowest byte of a register, e.g. AL, and the most significant digit in the second lowest byte, e.g. AH.

Adding

edit

Only the decimal numbers 0 to 99 can be added directly.

First the numbers are added as usual using add (or adc if you need the carry flag). The processor will set the adjust flag if the sum of both lower nibbles is 16 or higher, and the carry flag if the sum of both bytes is 256 or higher.

Then the result is adjusted, depending on the number representation.

  • Packed
    • The result is adjusted using daa (decimal adjust after addition): If the least significant nibble of the result is 10 or higher, or if the adjust flag is set, then the processor adds 6 to the result and discards any overflow of the nibble.
    • Then, if the most significant nibble of the result is 10 or higher, or if the carry flag is set, then the processor adds 96 (6 times 16) to the result and sets the carry flag.[2][3]
  • Unpacked
    • The result is adjusted using aaa (ASCII adjust after addition): If the least significant nibble of the result is 10 or higher, then the processor adds 6 to it and discards any overflow of the nibble, and stores it in the least significant byte.
    • The most significant byte is incremented.
    • Note that at this point the most significant byte may not contain a valid decimal number.[2][3]

Subtraction

edit

Only the decimal numbers 0 to 99 can be subtracted directly. First the numbers are subtracted as usual using sub (or sbb if you need the carry flag). The processor will set the adjust flag if a borrow occurred in the least significant nibble, and the carry flag if a borrow occurred in the most significant nibble.

  • Packed
    • The result is adjusted using das (decimal adjust after subtraction): If the least significant nibble of the result is 10 or higher, or if the adjust flag is set, then the processor subtracts 6 from the result.
    • Then, if the most significant nibble of the result is 10 or higher, or if the carry flag is set, then the processor subtracts 96 (6 times 16) from the result and sets the carry flag.[2][3]
  • Unpacked
    • The result is adjusted using aas (ASCII adjust after subtraction): If the least significant nibble of the result is 10 or higher, then the processor subtracts 6 from it and stores it in the least significant byte.
    • The most significant byte is decremented.
    • Note that at this point the most significant byte may not contain a valid decimal number.[2][3]

Multiplication

edit

Only unpacked representation is supported. Only two single digit numbers can be multiplied.

First the digits are multiplied as usual using mul.

Then the result is adjusted using aam (ASCII adjust for multiplication): The processor divides the result by ten, storing the quotient (just the integral part) in the most significant byte of the result and the remainder in the least significant byte of the result.[2][3]

Division

edit

Only unpacked representation is supported. Operands must fall in the range 0 to 99.

First the operands are converted to normal binary representation using aad (ASCII adjust before division): The processor converts numbers by multiplying the most significant byte by 10 and adding the least significant byte. The quotient and remainder of the division are obtained as usual using div, and will be present in normal binary representation.[2][3]

In x87

edit

The x87 coprocessor has BCD support in the form of a pair of load (FBLD) and store-and-pop (FBSTP) instructions. The former loads a 80-bit BCD integer into the FPU, while the latter writes a FPU value as a 80-bit integer value into the memory. Inside of the FPU, the values are stored as normal x87 extended-precision floats. Unlike the integer-facing versions, the two instructions remain available in long mode.[1]

The 80-bit format is divided into the following:

79 78 .. 72 71 .. 0
Sign Unused (0) 18 packed digits

There is a special "indefinite" value encoded as FFFFC000000000000000h.

Application

edit

Binary-coded decimal (BCD) numbers are used for storing decimal numbers, especially in financial software.[2]

The opcodes mentioned above give the x86 rudimentary BCD support.[2]

Alternatives

edit

Adding BCD numbers using these opcodes is a complex task, and requires many instructions to add even modest numbers. It can also require a large amount of memory.[2] If only doing integer calculations, then all integer calculations are exact, so the radix of the number representation is not important for accuracy. On an x86 processor, calculations with binary numbers are usually a lot faster than the same calculations with BCD numbers.[2]

See also

edit

References

edit
  1. ^ a b "4.7 BCD and packed BCD integers". Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1: Basic Architecture (PDF). Version 072. Vol. 1. Intel Corporation. 2020-05-27 [1997]. pp. 3–2, 4-9–4-11 [4-10]. 253665-072US. Archived (PDF) from the original on 2020-08-06. Retrieved 2020-08-06. […] When operating on BCD integers in general-purpose registers, the BCD values can be unpacked (one BCD digit per byte) or packed (two BCD digits per byte). The value of an unpacked BCD integer is the binary value of the low halfbyte (bits 0 through 3). The high half-byte (bits 4 through 7) can be any value during addition and subtraction, but must be zero during multiplication and division. Packed BCD integers allow two BCD digits to be contained in one byte. Here, the digit in the high half-byte is more significant than the digit in the low half-byte. […] When operating on BCD integers in x87 FPU data registers, BCD values are packed in an 80-bit format and referred to as decimal integers. In this format, the first 9 bytes hold 18 BCD digits, 2 digits per byte. The least-significant digit is contained in the lower half-byte of byte 0 and the most-significant digit is contained in the upper half-byte of byte 9. The most significant bit of byte 10 contains the sign bit (0 = positive and 1 = negative; bits 0 through 6 of byte 10 are don't care bits). Negative decimal integers are not stored in two's complement form; they are distinguished from positive decimal integers only by the sign bit. The range of decimal integers that can be encoded in this format is −1018 + 1 to 1018 − 1. The decimal integer format exists in memory only. When a decimal integer is loaded in an x87 FPU data register, it is automatically converted to the double-extended-precision floating-point format. All decimal integers are exactly representable in double extended-precision format. […] [1]
  2. ^ a b c d e f g h i j k l Hyde, Randall (September 2003). Decimal Arithmetic. No Starch Press. Archived from the original on 2008-11-02. Retrieved 2008-10-18. {{cite book}}: |work= ignored (help)
  3. ^ a b c d e f Volume 2A: Instruction Set Reference, A-M (PDF). Vol. 2A. Intel Corporation. 2007-05-17. Archived from the original (PDF) on 2008-03-15. Retrieved 2007-06-27. {{cite book}}: |work= ignored (help)