summaryrefslogtreecommitdiffstats
path: root/algorithm.tex
diff options
context:
space:
mode:
authorYann Herklotz <git@yannherklotz.com>2020-11-20 01:56:37 +0000
committerYann Herklotz <git@yannherklotz.com>2020-11-20 01:56:48 +0000
commitaa7b60a0270638109380b7d73fa58deeddd6158a (patch)
tree8122f83fc5292731785232f98b117f805ec187e3 /algorithm.tex
parent92dd944915df61e8277da389dd60a20b98ab7952 (diff)
downloadoopsla21_fvhls-aa7b60a0270638109380b7d73fa58deeddd6158a.tar.gz
oopsla21_fvhls-aa7b60a0270638109380b7d73fa58deeddd6158a.zip
Modify algorithm
Diffstat (limited to 'algorithm.tex')
-rw-r--r--algorithm.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/algorithm.tex b/algorithm.tex
index 5c98854..f9ce271 100644
--- a/algorithm.tex
+++ b/algorithm.tex
@@ -211,7 +211,7 @@ An HTL program thus consists of two maps: a control map that describes how to ca
%\node[scale=0.4] at (3.5,3.6) {$\cdots$};
%\node[scale=0.4] at (3.5,3.4) {\texttt{reg\_8}};
\end{tikzpicture}
- \caption{The FSMD for our running example.}\label{fig:accumulator_diagram}
+ \caption{The FSMD for our running example.\YH{Removed the register block because these are technically just internal to the update function. Also not sure if we should keep the RAM block because it is a bit misleading as we don't use those signals to communicate with the RAM, instead we just use a RAM.}}\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*}