# Integer arithmetic from a computer point of view

28 Oct 2018**work in progress**, so if you find it incomplete and not readable probably it's not finished yet. I prefer to publish a little before than leave a post to rust in my drafts.

A thing that is overlooked is the way arithmetic operations work in a computer and specifically in the processing unit: not having a clear idea of how the operations are performed and their limitations can cause very important bug to happen and also help in case you want to reverse unknown code.

## Integer encoding

We are interested of the case of a register containing a number: since
First of all, the arithmetic inside a CPU is done on register of fixed
size via the `ALU`

and since the register are size limited, all the
arithmetic operations are intended modulo the size of the registers.

the register has a fixed number of bits (let’s say is \(N\)) we can only represent (directly) unsigned values between \(0\) and \(2^N - 1\).

The formula is the following

Remember the following properties for binary numbers: **completness**

and **shifting - multiplication relation**

that means that left shifting a binary number is equivalent to multiplying the same number for a power of two (I know, I know, this is obvious).

For signed numbers there is not a unique way to represent them: the quick
and dirty way would be to use the most significant bit as **sign bit** but this has
the drawback to have two zeros.

I think that this encoding is not used by anyone in the real world (but I could be wrong), there are more efficient ways.

### One’s complement

It consists in flipping all the bits of a number, in this way if you define the negative of a given number as the one’s complement of it you have the nice property that this two numbers summed are equal to zero and you don’t have to implement any particular circuitery on the processor since the operations are executed as usual.

The problem is that you have two zeros: all bits equal to zero and all equal to one.

### Two’s complement

It’s an extension of the one’s complement: to obtain the negative representation of a number you have to take the one’s complement and add one: in this way you have an asymmetry between the minimum and maximum number that can be represented, i.e. you can represent values between \(-2^{N - 1}\) and \(2^{N - 1} - 1\). For example with 7 bits you have the interval \((-64, 63)\).

Normally in the code is this the way the negative numbers are represented.

Mind blowing realization is that the two’s complement of the lowest integer is itself:

Remember that a value into a register is not signed or unsigned by itself, it depends on how is used in the code.

## Operations

### Sign extension

In certain cases could be necessary to do operations between numbers having a different
number of bits; if these numbers are unsigned it’s not big deal, but if instead we having
signed ones we have to **sign extend** i.e. to complete the bits of the extended number
with all `1`

s.

Let me make an example: if we have a 8-bit register with the decimal value \(-16\),
its representation with two’s complement will be `0xef`

; now, if we want to put this
value into a 16-bit register and represent the same number, we have to set as most significant
byte `0xff`

, i.e. `0xffef`

: this because of a nice property of binary numbers, namely

in our case we have the Mth bit used for the sign and suppose we have other \(s\) bits

Some architectures have direct instructions to do that, like the movxs in x86, other instead use multiple operations to do the same

## Flags

It’s all fine and good but as already said, we have a limited number of bits
to represent numbers, so it’s possible that some operations couldn’t be done
correctly: for example, if you want to sum, in a 8bits-register `0xff`

to
any other number, you can’t fit the result in the register, you should have
one bit more; for this reason in a CPU you have also some flags (i.e. one-bit
values) usually contained in an unique register to indicate some particular
properties of the last arithmetic operation. Take in mind that not all
architectures have it.

Each system has its own nomenclature and specific flags, but I think the minimal set is composed of the following

### Carry flag

Used in unsigned numbers to indicate that the result doesn’t fit in the register.

### Overflow flag

Used for signed numbers to indicate that the resulting sign bit is not coherent with the correct result; for example with 4-bit (binary) numbers we can have the following four cases:

### Zero flag

The last operation resulted in a result equal to zero, like subtracting two registers containing
the same value or doing the logical `and`

operation between two registers having both zero as value.

## Flow control

At the end of the day the flags are used primarly to do the so called **flow control** that in
high level languages is implemented via `if`

, `while`

, `for`

, etc…

Each architecture implements this with some particular couple of family of instructions:one family to
set the flag, like `cmp`

and `test`

, and another to jump to a particular location depending on the
particular values the flags have, like `jmp`

, `jne`

, `jnz`

and so on in `x86`

or `b`

, `bne`

, `ble`

etc… in `ARM`

;

## Programmation errors

### Out of bounds

### Signedness

### Overflow

### Wrap

### Conversion

### Undefined behaviour

Having an asymmetry between the size of the greatest positive and lowest negative in two’s complement arithmetics
causes some particular behaviour to happen for some functions: take for example the `abs()`

one; this function
returns the positive version of (almost) any number, indeed what is the positive value of the lowest negative
possible in a given architecture (in two’s complement arithmetics)? From the man page we can read that
`Trying to take the absolute value of the most negative integer is not defined.`

so the following
code is not doing what you would expect when is passed `INT_MIN`

as argument

```
#define MAX_VALUE 5000
char buffer[MAX_VALUE];
int arg1 = atoi(argv[1]);
if (abs(arg1) < MAX_VALUE) {
buffer[arg1] = arg2;
}
```

## Links

- The CARRY flag and OVERFLOW flag in binary arithmetic
- Intel x86 JUMP quick reference
- SEI CERT C Coding Standard
- Condition Codes 1: Condition Flags and Codes from ARM site

**work in progress**. Let me know how do you want this to be completed