FLOATING POINT ARITHMETIC P&H Slides ECE 411 – Spring 2005

3/28/05ECE Spring Review of Numbers Computers are made to deal with numbers What can we represent in N bits? Unsigned integers: 0to2 N - 1 Signed Integers (Two’s Complement) -2 (N-1) to 2 (N-1) - 1

3/28/05ECE Spring Other Numbers What about other numbers? Very large numbers? (seconds/century) 3,155,760, ( x 10 9 ) Very small numbers? (atomic diameter) ( x ) Rationals (repeating pattern)2/3 ( ) Irrationals 2 1/2 ( ) Transcendentalse ( ),  ( ) All represented in scientific notation

3/28/05ECE Spring Scientific Notation (in Decimal) x radix (base) decimal pointmantissa exponent Normalized form: no leadings 0s (exactly one digit to left of decimal point) Alternatives to representing 1/1,000,000,000 Normalized: 1.0 x Not normalized: 0.1 x 10 -8,10.0 x

3/28/05ECE Spring Scientific Notation (in Binary) 1.0 two x 2 -1 radix (base) “binary point” exponent Computer arithmetic that supports it called floating point, because it represents numbers where the binary point is not fixed, as it is for integers Declare such variable in C as float mantissa

3/28/05ECE Spring Floating Point Representation Normal format: +1.xxxxxxxxxx two *2 yyyy two Multiple of Word Size (32 bits) 0 31 SExponent Significand 1 bit8 bits23 bits S represents SignExponent represents y’sSignificand represents x’s Represent numbers ranging from (1.0) to ( ) ie. from 1.18 x to 3.40 x 10 38

3/28/05ECE Spring Floating Point Representation What if result too large? (> 2.0x10 38 ) Overflow! Overflow  Exponent larger than represented in 8-bit Exponent field What if result too small? (>0, < 2.0x ) Underflow! Underflow  Negative exponent larger than represented in 8-bit Exponent field How to reduce chances of overflow or underflow?

3/28/05ECE Spring Double Precision Fl. Pt. Representation Next Multiple of Word Size (64 bits) Double Precision (vs. Single Precision) C variable declared as double Represent numbers almost as small as 2.0 x to almost as large as 2.0 x But primary advantage is greater accuracy due to larger significand 0 31 SExponent Significand 1 bit11 bits20 bits Significand (cont’d) 32 bits

3/28/05ECE Spring QUAD Precision Fl. Pt. Representation Next Multiple of Word Size (128 bits) Unbelievable range of numbers Unbelievable precision (accuracy) This is currently being worked on The current version has 15 bits for the exponent and 112 bits for the significand

3/28/05ECE Spring IEEE 754 Floating Point Standard (1/4) Single Precision, DP similar Sign bit:1 means negative 0 means positive Significand: To pack more bits, leading 1 implicit for normalized numbers bits single, bits double always true: Significand < 1 (for normalized numbers) Note: 0 has no leading 1, so reserve exponent value 0 just for number 0

3/28/05ECE Spring IEEE 754 Floating Point Standard (2/4) We want FP numbers to be used even if no FP hardware; e.g., sort records with FP numbers using integer compares Could break FP number into 3 parts: compare signs, then compare exponents, then compare significands Wanted it to be faster, single compare if possible, especially if positive numbers Then want order: Highest order bit is sign ( negative < positive) Exponent next, so big exponent => bigger # Significand last: exponents same => bigger #

3/28/05ECE Spring IEEE 754 Floating Point Standard (3/4) Negative Exponent? 2’s comp? 1.0 x 2 -1 v. 1.0 x2 +1 (1/2 v. 2) / This notation using integer compare of 1/2 v. 2 makes 1/2 > 2! Instead, pick notation is most negative, and is most positive 1.0 x 2 -1 v. 1.0 x2 +1 (1/2 v. 2) 1/

3/28/05ECE Spring IEEE 754 Floating Point Standard (4/4) Called Biased Notation, where bias is number subtract to get real number IEEE 754 uses bias of 127 for single prec. Subtract 127 from Exponent field to get actual value for exponent 1023 is bias for double precision Summary (single precision): 0 31 SExponent Significand 1 bit8 bits23 bits (-1) S x (1 + Significand) x 2 (Exponent-127) Double precision identical, except with exponent bias of 1023

3/28/05ECE Spring Understanding the Significand (1/2) Method 1 (Fractions): In decimal: => / => / In binary: => / = 6 10 /8 10 => 11 2 /100 2 = 3 10 /4 10 Advantage: less purely numerical, more thought oriented; this method usually helps people understand the meaning of the significand better

3/28/05ECE Spring Understanding the Significand (2/2) Method 2 (Place Values): Convert from scientific notation In decimal: = (1x10 0 ) + (6x10 -1 ) + (7x10 -2 ) + (3x10 -3 ) + (2x10 -4 ) In binary: = (1x2 0 ) + (1x2 -1 ) + (0x2 -2 ) + (0x2 -3 ) + (1x2 -4 ) Interpretation of value in each position extends beyond the decimal/binary point Advantage: good for quickly calculating significand value; use this method for translating FP numbers

3/28/05ECE Spring Example: Converting Binary FP to Decimal Sign: 0 => positive Exponent: two = 104 ten Bias adjustment: = -23 Significand: 1 + 1x x x x x = = 1.0 ten ten Represents: ten *2 -23 ~ 1.986*10 -7 (about 2/10,000,000)

3/28/05ECE Spring Converting Decimal to FP (1/3) Simple Case: If denominator is an exponent of 2 (2, 4, 8, 16, etc.), then it’s easy. Show MIPS representation of = -3/4 -11 two /100 two = two Normalized to -1.1 two x 2 -1 (-1) S x (1 + Significand) x 2 (Exponent-127) (-1) 1 x ( ) x 2 ( )

3/28/05ECE Spring Converting Decimal to FP (2/3) Not So Simple Case: If denominator is not an exponent of 2. Then we can’t represent number precisely, but that’s why we have so many bits in significand: for precision Once we have significand, normalizing a number to get the exponent is easy. So how do we get the significand of a neverending number?

3/28/05ECE Spring Converting Decimal to FP (3/3) Fact: All rational numbers have a repeating pattern when written out in decimal. Fact: This still applies in binary. To finish conversion: Write out binary number with repeating pattern. Cut it off after correct number of bits (different for single v. double precision). Derive Sign, Exponent and Significand fields.

3/28/05ECE Spring : : : : -7 5: : -15 7: -7 * 2^129 8: -129 * 2^7 Peer Instruction What is the decimal equivalent of the floating pt # above?

3/28/05ECE Spring Peer Instruction Answer What is the decimal equivalent of: SExponentSignificand (-1) S x (1 + Significand) x 2 (Exponent-127) (-1) 1 x ( ) x 2 ( ) -1 x (1.111) x 2 (2) 1: : : : -7 5: : -15 7: -7 * 2^129 8: -129 * 2^

3/28/05ECE Spring “And in conclusion…” Floating Point numbers approximate values that we want to use. IEEE 754 Floating Point Standard is most widely accepted attempt to standardize interpretation of such numbers Every desktop or server computer sold since ~1997 follows these conventions Summary (single precision): 0 31 SExponent Significand 1 bit8 bits23 bits (-1) S x (1 + Significand) x 2 (Exponent-127) Double precision identical, bias of 1023

More Floating Point

3/28/05ECE Spring Representation for ± ∞ In FP, divide by 0 should produce ± ∞, not overflow. Why? OK to do further computations with ∞ E.g., X/0 > Y may be a valid comparison IEEE 754 represents ± ∞ Most positive exponent reserved for ∞ Significands all zeroes

3/28/05ECE Spring Representation for 0 Represent 0? exponent all zeroes significand all zeroes too What about sign? +0: : Why two zeroes? Helps in some limit comparisons

3/28/05ECE Spring Special Numbers What have we defined so far? (Single Precision) ExponentSignificandObject 000 0nonzero??? 1-254anything+/- fl. pt. # 2550+/- ∞ 255nonzero??? Professor Kahan had clever ideas; “Waste not, want not” Exp=0,255 & Sig!=0 …

3/28/05ECE Spring Representation for Not a Number What is sqrt(-4.0) or 0/0 ? If ∞ not an error, these shouldn’t be either. Called Not a Number (NaN) Exponent = 255, Significand nonzero Why is this useful? Hope NaNs help with debugging? They contaminate: op(NaN, X) = NaN

3/28/05ECE Spring Representation for Denorms (1/2) Problem: There’s a gap among representable FP numbers around 0 Smallest representable pos num: a = 1.0… 2 * = Second smallest representable pos num: b = 1.000……1 2 * = a - 0 = b - a = b a Gaps! Normalization and implicit 1 is to blame!

3/28/05ECE Spring Representation for Denorms (2/2) Solution: We still haven’t used Exponent = 0, Significand nonzero Denormalized number: no leading 1, implicit exponent = Smallest representable pos num: a = Second smallest representable pos num: b =

3/28/05ECE Spring Overview Reserve exponents, significands: ExponentSignificandObject 000 0nonzeroDenorm 1-254anything+/- fl. pt. # 2550+/- ∞ 255nonzeroNaN

3/28/05ECE Spring Rounding Math on real numbers  we worry about rounding to fit result in the significant field. FP hardware carries 2 extra bits of precision, and rounds for proper value Rounding occurs when converting… double to single precision floating point # to an integer

3/28/05ECE Spring IEEE Four Rounding Modes Round towards + ∞ ALWAYS round “up”: 2.1  3, -2.1  -2 Round towards - ∞ ALWAYS round “down”: 1.9  1, -1.9  -2 Truncate Just drop the last bits (round towards 0) Round to (nearest) even (default) Normal rounding, almost: 2.5  2, 3.5  4 Like you learned in grade school Insures fairness on calculation Half the time we round up, other half down

3/28/05ECE Spring Integer Multiplication (1/3) Paper and pencil example (unsigned): Multiplicand10008 Multiplier x m bits x n bits = m + n bit product

3/28/05ECE Spring Integer Multiplication (2/3) In MIPS, we multiply registers, so: 32-bit value x 32-bit value = 64-bit value Syntax of Multiplication (signed): mult register1, register2 Multiplies 32-bit values in those registers & puts 64-bit product in special result regs: puts product upper half in hi, lower half in lo hi and lo are 2 registers separate from the 32 general purpose registers Use mfhi register & mflo register to move from hi, lo to another register

3/28/05ECE Spring Integer Multiplication (3/3) Example: in C: a = b * c; in MIPS: let b be $s2; let c be $s3; and let a be $s0 and $s1 (since it may be up to 64 bits) mult $s2,$s3# b*c mfhi $s0# upper half of # product into $s0 mflo $s1# lower half of # product into $s1 Note: Often, we only care about the lower half of the product.

3/28/05ECE Spring Integer Division (1/2) Paper and pencil example (unsigned): 1001 Quotient Divisor 1000| Dividend Remainder (or Modulo result) Dividend = Quotient x Divisor + Remainder

3/28/05ECE Spring Integer Division (2/2) Syntax of Division (signed): div register1, register2 Divides 32-bit register 1 by 32-bit register 2: puts remainder of division in hi, quotient in lo Implements C division ( / ) and modulo ( % ) Example in C: a = c / d; b = c % d; in MIPS: a  $s0;b  $s1;c  $s2;d  $s3 div $s2,$s3# lo=c/d, hi=c%d mflo $s0# get quotient mfhi $s1# get remainder

3/28/05ECE Spring Unsigned Instructions & Overflow MIPS also has versions of mult, div for unsigned operands: multu divu Determines whether or not the product and quotient are changed if the operands are signed or unsigned. MIPS does not check overflow on ANY signed/unsigned multiply, divide instr Up to the software to check hi

3/28/05ECE Spring FP Addition & Subtraction Much more difficult than with integers (can’t just add significands) How do we do it? De-normalize to match larger exponent Add significands to get resulting one Normalize (& check for under/overflow) Round if needed (may need to renormalize) If signs ≠, do a subtract. (Subtract similar) If signs ≠ for add (or = for sub), what’s ans sign? Question: How do we integrate this into the integer arithmetic unit? [Answer: We don’t!]

3/28/05ECE Spring MIPS Floating Point Architecture (1/4) Separate floating point instructions: Single Precision: add.s, sub.s, mul.s, div.s Double Precision: add.d, sub.d, mul.d, div.d These are far more complicated than their integer counterparts Can take much longer to execute

3/28/05ECE Spring MIPS Floating Point Architecture (2/4) Problems: Inefficient to have different instructions take vastly differing amounts of time. Generally, a particular piece of data will not change FP  int within a program. Only 1 type of instruction will be used on it. Some programs do no FP calculations It takes lots of hardware relative to integers to do FP fast

3/28/05ECE Spring MIPS Floating Point Architecture (3/4) 1990 Solution: Make a completely separate chip that handles only FP. Coprocessor 1: FP chip contains bit registers: $f0, $f1, … most of the registers specified in.s and.d instruction refer to this set separate load and store: lwc1 and swc1 (“load word coprocessor 1”, “store …”) Double Precision: by convention, even/odd pair contain one DP FP number: $f0 / $f1, $f2 / $f3, …, $f30 / $f31 Even register is the name

Floating Point (a brief look) We need a way to represent numbers with fractions, e.g., very small numbers, e.g., very large numbers, e.g.,  10 9 Representation: sign, exponent, significand: (–1) sign  significand  2 exponent more bits for significand gives more accuracy more bits for exponent increases range IEEE 754 floating point standard: single precision: 8 bit exponent, 23 bit significand double precision: 11 bit exponent, 52 bit significand

IEEE 754 floating-point standard Leading “1” bit of significand is implicit Exponent is “biased” to make sorting easier all 0s is smallest exponent all 1s is largest bias of 127 for single precision and 1023 for double precision summary: (–1) sign  significand)  2 exponent – bias Example: decimal: -.75 = - ( ½ + ¼ ) binary: -.11 = -1.1 x 2 -1 floating point: exponent = 126 = IEEE single precision:

3/28/05ECE Spring Floating point addition

Floating Point Complexities Operations are somewhat more complicated (see text) In addition to overflow we can have “underflow” Accuracy can be a big problem IEEE 754 keeps two extra bits, guard and round four rounding modes positive divided by zero yields “infinity” zero divide by zero yields “not a number” other complexities Implementing the standard can be tricky Not using the standard can be even worse see text for description of 80x86 and Pentium bug!