summaryrefslogtreecommitdiffstats
path: root/evaluation.tex
diff options
context:
space:
mode:
authorn.ramanathan14 <n.ramanathan14@imperial.ac.uk>2020-11-16 22:31:20 +0000
committeroverleaf <overleaf@localhost>2020-11-17 09:47:51 +0000
commit6b2fce9cf4710f7caa489a7fafde97f0d94ed4b9 (patch)
treef75247fa8ac8d42bc93fcc72ea7dcc02d5b87892 /evaluation.tex
parentdb40aeb048b663cae042eeec070b8607dba8f10f (diff)
downloadoopsla21_fvhls-6b2fce9cf4710f7caa489a7fafde97f0d94ed4b9.tar.gz
oopsla21_fvhls-6b2fce9cf4710f7caa489a7fafde97f0d94ed4b9.zip
Update on Overleaf.
Diffstat (limited to 'evaluation.tex')
-rw-r--r--evaluation.tex10
1 files changed, 10 insertions, 0 deletions
diff --git a/evaluation.tex b/evaluation.tex
index cb185ac..aada207 100644
--- a/evaluation.tex
+++ b/evaluation.tex
@@ -1,4 +1,14 @@
\section{Evaluation}
+\NR{
+To-do list:
+\begin{itemize}
+ \item Modifying the final checks of Polybench programs
+ \item Re-synthesis the polybench programs
+ \item Collect new compile times of Vericert
+ \item Collate the csv file again
+ % \item Re-run and synthesis adpcm and gsm with new Vericert for Table~\ref{tab:chstone}
+\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.}
\begin{description}