summaryrefslogtreecommitdiffstats
path: root/evaluation.tex
diff options
context:
space:
mode:
authorJohn Wickerson <j.wickerson@imperial.ac.uk>2020-11-10 13:41:46 +0000
committeroverleaf <overleaf@localhost>2020-11-12 10:54:46 +0000
commita758545c7c61d7861404fb43b8b20e644fd2a7fd (patch)
tree0538b35e212c1336332493a3ac8a7e2e426ce965 /evaluation.tex
parente87f0d5314b30f0e485a5103bc71e49871052714 (diff)
downloadoopsla21_fvhls-a758545c7c61d7861404fb43b8b20e644fd2a7fd.tar.gz
oopsla21_fvhls-a758545c7c61d7861404fb43b8b20e644fd2a7fd.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 8f49de1..b81d08d 100644
--- a/evaluation.tex
+++ b/evaluation.tex
@@ -1,6 +1,6 @@
\section{Evaluation}
-Our evaluation is designed to answer the following three research questions.
+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.}
\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?