summaryrefslogtreecommitdiffstats
path: root/evaluation.tex
diff options
context:
space:
mode:
authorJohn Wickerson <j.wickerson@imperial.ac.uk>2020-11-18 16:48:11 +0000
committeroverleaf <overleaf@localhost>2020-11-18 17:00:38 +0000
commit39f082f7e000b23f19275b5c1cf9eae0ac4d4164 (patch)
tree4326bb9a2f172bd59f108979bed148f5a5011d20 /evaluation.tex
parent4b223157aac969ce182c808538d002c2b207d914 (diff)
downloadoopsla21_fvhls-39f082f7e000b23f19275b5c1cf9eae0ac4d4164.tar.gz
oopsla21_fvhls-39f082f7e000b23f19275b5c1cf9eae0ac4d4164.zip
Update on Overleaf.
Diffstat (limited to 'evaluation.tex')
-rw-r--r--evaluation.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/evaluation.tex b/evaluation.tex
index 5d2034e..b5f806c 100644
--- a/evaluation.tex
+++ b/evaluation.tex
@@ -11,7 +11,7 @@ To-do list:
\end{itemize}
}
-Our evaluation is designed to answer the following three research questions. \JW{How about adding one more RQ at the start called `How reliable is the hardware generated by \vericert{}, and how does this compare to existing HLS tools?' Then you can answer this by saying that you couldn't break your tool using the Csmith programs generated by Du et al., which did break all the other HLS tools.}
+Our evaluation is designed to answer the following three research questions.
\begin{description}
\item[RQ1] How fast is the hardware generated by \vericert{}, and how does this compare to existing HLS tools?
\item[RQ2] How area-efficient is the hardware generated by \vericert{}, and how does this compare to existing HLS tools?