summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--algorithm.tex1
1 files changed, 0 insertions, 1 deletions
diff --git a/algorithm.tex b/algorithm.tex
index c2a676c..6c02326 100644
--- a/algorithm.tex
+++ b/algorithm.tex
@@ -218,7 +218,6 @@ An HTL program thus consists of two maps: a control map that describes how to ca
\node[scale=0.4] at (3.5,3.4) {\texttt{reg\_8}};
\end{tikzpicture}
\caption{The FSMD for the example shown in Figure~\ref{fig:accumulator_c_rtl}, split into a data path and control logic for the next state calculation. The Update block takes the current state, current values of all registers and at most one value stored in the array, and calculates a new value that can either be stored back in the array or in a register.}\label{fig:accumulator_diagram}
-%\JW{Maybe replace `State' with `Current State'? And maybe `Calculate State' could be clearer as `Calculate Next State'?} \JW{Can state 15 (or should it be state 16??) have a dangling incoming arrow to indicate that it is the start state? And perhaps state 1 could have a double outline to indicate that it is an `accepting' state? Since there's space above the `Calculate State' box, I'd be mildly in favour of expanding that box a bit so that it included all 15 states explicitly (snaking back and forth).}\YH{If this is better I can mock up a tikz version of it maybe and fix the last bits then too.}
\end{figure*}
\paragraph{Translating memory}