This presentation is the property of its rightful owner.
1 / 27

# Presenter PowerPoint PPT Presentation

Presenter. MaxAcademy Lecture Series – V1.0, September 2011. Number Representations and Arithmetic. Lecture Overview. Why we care Number representation Number types in MaxCompiler Rounding Arithmetic styles Error and other numerics issues. Why we care.

Presenter

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

#### Presentation Transcript

Presenter

MaxAcademy Lecture Series – V1.0, September 2011

Number Representationsand Arithmetic

### Lecture Overview

• Why we care

• Number representation

• Number types in MaxCompiler

• Rounding

• Arithmetic styles

• Error and other numerics issues

### Why we care

• Performance depends on the number of arithmetic units that fit in the FPGA  lower precision = more units = higher performance

• Accuracy and performance may be competing objectives

• FPGA resource usage depends on data representation and bitwidths

• Custom computers give us greater control over number representation, but we need to achieve enough accuracy with small enough resource usage

### Number Representation

• Microprocessors:

- Integer: unsigned, two’s complement

- Floating Point

• others:

• Fixed point

• Logarithmic number representation

• Redundant number systems: use more bits

• Signed-digit representation

• Residue number system (modulo arithmetic)

• Decimal: decimal floating point, binary coded decimal

Unsigned

Representations

0000

1111

0001

0

15

1

1110

0

0010

-0

+1

14

2

-1

+2

1101

0011

13

3

+3

-2

Signed Values

(1’s Complement)

4

0100

+4

-3

12

-

1100

+

+5

-4

5

0101

11

+6

-5

1011

6

+7

-6

0110

-7

10

7

1010

9

8

0111

1001

1000

Unsigned

Representations

0000

1111

0001

0

15

1

1110

0

0010

-1

+1

14

2

-2

+2

1101

0011

13

3

+3

-3

Signed Values

(2’s Complement)

4

0100

+4

-4

12

-

1100

+

+5

-5

5

0101

11

+6

-6

1011

6

+7

-7

0110

-8

10

7

1010

9

8

0111

1001

1000

### Signed N-bit Integers

• Sign-magnitude representation for integer x.

Most significant bit (msb) is the sign bit.

• One’s complement numbers:

Represent -x by inverting each bit. Overflow=Sign_Carry_In ^ Sign_Carry_Cout

• Two’s complement:

Represent -x by inverting each bit and adding ‘1’. Overflow=same as One’s c.

### Fixed Point Numbers

• Generalisation of integers, with a ‘radix point’

• Digits to the right of the radix point represent negative powers of 2

• F = number of fractional bits

• Bits to the right of the ‘radix point’

• For integers, F = 0

Digit weights:

(unsigned)

I bits

F bits

### Fixed Point Maths

• Think of each number as: (V  2-F)

• Addition and subtraction: (V1  2-F1) + (V2  2-F2)

• Align radix points and compute the same as for integers

• Multiplication: (V1  2-F1)  (V2  2-F2) = V1V2  2-(F1+F2)

• Division: (V1  2-F1) / (V2  2-F2) = (V1/V2)  2-(F1-F2)

+

=

=

### Floating Point Representation

• regular mantissa = 1.xxxxxx

• denormal numbers: mantissa = 0.xxxxxx with min exponent

• IEEE FP Standard: base=2, single, double, extended widths

• Custom Computing: choose widths of fields + choose base

• Performance:small widths, larger base, truncation.

• versus Accuracy: wide, base=2, round to even.

• Disadvantage: FP arithmetic units tend to be very large compared to Integer/fixed point units.

### Floating Point Maths

• Align exponents: shift smaller mantissa to the larger number’s exponent

• Normalize: shift mantissa until starts with ‘1’, adjust exponent

• Multiplication:

• Division:

• Divide mantissas, subtract exponents

### Number Representation in MaxCompiler

• MaxCompiler has in-built support for floating point and fixed point/integer arithmetic

• Depends on the type of the HWVar

• Can type inputs, outputs and constants

• Or can castHWVars from one type to another

• Types are Java objects, just like HWVars,

// Create an input of type t

HWVario.input(String name, HWType t);

// Create an HWVar of type t with constant value

HWVar constant.var(HWType t, double value);

// Cast HWVary to type t

HWVar x = y.cast(HWType t);

### hwFloat

• Floating point numbers with base 2, flexible exponent and mantissa

• Compatible with IEEE floating point exceptdoes not support denormal numbers

• In custom computers choose to use a larger exponent

• Examples:

HWType t = hwFloat(intexponent_bits, intmantissa_bits);

Including the sign bit

Why hwFloat(7,17)…?

### hwFix

• Fixed point numbers

• Flexible integer and fraction bits

• Flexible sign mode

• SignMode.UNSIGNED or SignMode.TWOSCOMPLEMENT

• Common cases have useful aliases

HWType t = hwFix(intinteger_bits, intfraction_bits, SignModesm);

### Mixed Types

• Can mix different types in a MaxCompiler kernel to use the most appropriate type for each operation

• Type conversions costs area – must cast manually

• Types can be parameter to a kernel program

• Can generate the same kernel with different types

class MyKernel extends Kernel {

public MyKernel(KernelParameters k, HWTypet_in, HWTypet_out) {

super(k);

HWVar p = io.input(“p”, hwFloat(8,24));

HWVar q = io.input(“q”, t_in);

HWVar r = p * p;

HWVar s = r + q.cast(r.getType());

io.output(“s”, s.cast(t_out), t_out);

}

}

### Rounding

• When we remove bits from the RHS of a number we may want to perform rounding.

• Casting / type conversion

• Inside arithmetic operations

• Different possibilities

• TRUNCATE: throw away unwanted bits

• TONEAR: if >=0.5, round up (add 1)

• TONEAREVEN: if >0.5 round up, if <0.5 round down, if =0.5 then round to the nearest even number

• Lots of less common alternatives:

• Towards zero, towards positive infinity, towards negative infinity, random….

• Very important in iterative calculations – may affect convergence behaviour

### Rounding in MaxCompiler

• Floating point arithmetic uses TONEAREVEN

• Fixed point rounding is flexible, controlled by the RoundingMode

• TRUNCATE, TONEAR and TONEAREVEN are in-built

HWVar z;

...

optimization.pushRoundingMode(RoundingMode.TRUNCATE);

z = z.cast(smaller_type);

optimization.popRoundingMode();

### Arithmetic Styles

Parallel

Digit-Serial

Sequential

- loop x times

Pipelined

- loop unrolled

Combinational

- loop unrolled

- no registers

- logic minimization

### Arithmetic in MaxCompiler

• By default uses deeply pipelined arithmetic functions

• Objective is high operating frequency

• Can reduce pipelining gradually to produce combinatorial functions, controlled by pushing and popping a “pipelining factor”

• 1.0 = maximum pipelining ; 0.0 = no pipelining

HWVar x, y, z; // floating point numbers

...

z = x * y; // fully pipelined

optimization.pushPipeliningFactor(0.5);

z += x; // half pipelined – lower latency

optimization.pushPipeliningFactor(0.0);

z += y; // no pipelining

optimization.popPipeliningFactor();

optimization.popPipeliningFactor();

z = z * 2; // fully pipelined again

### Cost for arithmetic

• ~1 LUT/bit for fixed point, hundreds of LUTs for floating point

• Multiplication: Can use DSP blocks

• 18x25bit multiply on Xilinx

• Number of DSPs depends on total bits (fixed point) or mantissa bitwidth (floating point)

Approximate cost models

I = Integer bits, F = Fraction bits. E = Exponent bits, M = Mantissa Bits

M

N

### Benefits of Fixed Point

• Consider fixed point compared to single precision floating point

• If range is tightly confined, we could use 24-bit fixed point

• If data has a wider range, may need 32-bit fixed point

• Arithmetic is not 100% of the chip. In practice, often see ~5x performance boost from fixed point.

### Error

• A,B:. A (op) B = result + error

• Floating point introduces (dynamic) relative error

• Error = f(exponent of result)  relative error

• Fixed point introduces (static) absolute error

• Error = f(rightmost bit position of result)  static error

• Error is minimized by good rounding

### Other numerics issues

• Overflow

• Number is too large (positive or negative) to be represented

• Usually catastrophic – important data is lost/invalid

• Underflow

• Number is too small to be represented and rounds to zero

• With fixed point, happens gradually

• With floating point without denormals, happens suddenly

• Usually underflowing data is not so important (numbers are very small)

• Bias

• If errors do not have a mean of zero, they will grow with repeated computation.

• Big issue in iterative calculations  numbers gradually get more and more wrong!

• TONEAREVEN rounding mode minimizes bias

### Further Reading on Computer Arithmetic

• Goldberg, “What Every Computer Scientist Should Know About Floating-Point Arithmetic”, ACM Computing Surveys, March 1991

• Textbooks:

• Koren, “Computer Arithmetic Algorithms,” 1998.

• Pahrami, ”Computer Arithmetic: Algorithms and Hardware Designs,” Oxford University Press, 2000.

• Waser, Flynn, “Introduction for Arithmetic for Digital Systems Designers,” Holt, Rinehard & Winston, 1982.

• Omondi, “Computer Arithmetic Systems,” Prentice Hall, 1994.

• Hwang, “Computer Arithmetic: Principles, Architectures and Design,” Wiley, 1978.

### Exercises

• Write a MaxCompiler kernel that takes one hwFloat(8,24) input stream and adds it to a hwFloat(11, 53)input stream to produce a hwFloat(11, 53) result.

• What will be the result of trying to represent X=232 and Y=2-2 in each of the following number types:

• Construct a test to show the difference between rounding modes on a multiplication operation of two hwFix(4, 4, TWOSCOMPLEMENT) numbers. Vary the number of fraction bits – what is the impact on the bias difference between TONEAR and TONEAREVEN and why?

hwFix(32, 0, UNSIGNED)

hwFix(32, 0, TWOSCOMPLEMENT)

hwFix(28, 4, UNSIGNED)

hwFix(32, 4, UNSIGNED)

hwFloat(11, 53)

hwFloat(8, 24)

hwFloat(8, 32)

hwFloat(8, 33)