X-Git-Url: https://git.ucc.asn.au/?p=ipdf%2Fsam.git;a=blobdiff_plain;f=chapters%2FBackground%2FFloats.tex;fp=chapters%2FBackground%2FFloats.tex;h=7eba8a27bdb4c963fc54a389ad95e272e34525a7;hp=0000000000000000000000000000000000000000;hb=9fcf44a0c34f393689118e913a2d17d907036c85;hpb=d5e7e14d2ec624cfe0febcccd81e95082ef1c175

diff --git a/chapters/Background/Floats.tex b/chapters/Background/Floats.tex
new file mode 100644
index 0000000..7eba8a2
--- /dev/null
+++ b/chapters/Background/Floats.tex
@@ -0,0 +1,14 @@
+\input{chapters/Background/Floats/Definition}
+\subsection{Visualisation of Floating Point Representation}
+\input{chapters/Background/Floats/Visualisation}
+
+
+%\subsection{Floating Point Operations}
+%\input{chapters/Background/Floats/Operations}
+
+
+\subsection{Arbitrary Precision Floating Point Numbers}
+
+Arbitrary precision floating point numbers are implemented in a variety of software libraries which will dynamically allocate extra bits for the exponent or mantissa as required. An example is the GNU MPFR library discussed by Fousse in 2007\cite{fousse2007mpfr}. Although many arbitrary precision libraries already existed, MPFR intends to be fully compliant with some of the more obscure IEEE-754 requirements such as rounding rules and exceptions. 
+
+As we have seen, it is trivial to find real numbers that would require an infinite number of bits to represent exactly. Implementations of ``arbitrary'' precision must carefully determine at what point rounding should occur so as to balance performance with memory usage.