summaryrefslogtreecommitdiffstats
path: root/evaluation.tex
diff options
context:
space:
mode:
authorYann Herklotz <ymh15@ic.ac.uk>2021-04-17 10:43:17 +0000
committeroverleaf <overleaf@localhost>2021-04-17 11:11:05 +0000
commitc1796951a900b58dfe339809df8204221e8f1a54 (patch)
treed01d988d12bc6e7b11bd82657b25e96377006c33 /evaluation.tex
parent204b9b668aa418fbab1ed8b591f2cf7fabb6bc2c (diff)
downloadoopsla21_fvhls-c1796951a900b58dfe339809df8204221e8f1a54.tar.gz
oopsla21_fvhls-c1796951a900b58dfe339809df8204221e8f1a54.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 1d800e4..9cf8d9e 100644
--- a/evaluation.tex
+++ b/evaluation.tex
@@ -166,7 +166,7 @@ By looking at the median, when division/modulo operations are enabled, we see th
\subsection{RQ3: How quickly does \vericert{} translate the C into Verilog?}
-\vericert{} takes around 0.1$\times$ as long as \legup{} to perform the translation from C into Verilog, showing at least that verification does not have a substantial effect on the run-time of the HLS tool. However, this is a meaningless victory, as a lot of the extra time that \legup{} uses is on performing computationally heavy optimisations such as loop pipelining and scheduling.
+\legup{} takes around 10$\times$ as long as \vericert{} to perform the translation from C into Verilog, showing at least that verification does not have a substantial effect on the run-time of the HLS tool. However, this is a meaningless victory, as a lot of the extra time that \legup{} uses is on performing computationally heavy optimisations such as loop pipelining and scheduling.
%%% Local Variables:
%%% mode: latex