X-Git-Url: https://git.stderr.nl/gitweb?a=blobdiff_plain;f=christiaan%2Freductioncircuit.lhs;h=a41dbf6dfb46fb89d4bf4047b90a23192659cf84;hb=a32353a119937722388b8a78e73ab6e269484bca;hp=be3c2d60d601cf1ae64f632c9847a11d7b1ddb06;hpb=5bfc71c197897497ac6520548fe3e405dc5f9a9b;p=matthijs%2Fmaster-project%2Ffinal-presentation.git

diff --git a/christiaan/reductioncircuit.lhs b/christiaan/reductioncircuit.lhs
index be3c2d6..a41dbf6 100644
--- a/christiaan/reductioncircuit.lhs
+++ b/christiaan/reductioncircuit.lhs
@@ -3,14 +3,14 @@
 \frame{
 \frametitle{Too Restrictive?}
 \begin{itemize}
-  \item Is CλasH too restrictive given the fact that a designer can currently not define his own vector transformations, or recursive functions for that matter?
+  \item Is \clash{} too restrictive given the fact that a designer can currently not define his own vector transformations, or recursive functions for that matter?
 \end{itemize}
 }
 
 \frame{
 \frametitle{Too Restrictive?}
 \begin{itemize}
-  \item There is certainly room to increase expressivity. But we can already describe non-trivial design in CλasH.
+  \item There is certainly room to increase expressivity. But we can already describe non-trivial design in \clash{}.
   \item Example: Reduction circuit
 \end{itemize}
 }
@@ -95,7 +95,7 @@ fifo :: (State (Fifo {..})) (inp, shift) =
   \item Map all vectors to RAMs:
   \begin{itemize}
     \item Store length separately, extra logic
-    \item What happens if size exceeds size of 1 blockRAM?
+    \item What happens if size of the vector exceeds size of the size of the RAM?
   \end{itemize}
   \item Translate to (shift/circular) Buffers
   \begin{itemize}