summaryrefslogtreecommitdiffstats
path: root/main.tex
diff options
context:
space:
mode:
Diffstat (limited to 'main.tex')
-rw-r--r--main.tex44
1 files changed, 44 insertions, 0 deletions
diff --git a/main.tex b/main.tex
index 95a6b7b..2e05268 100644
--- a/main.tex
+++ b/main.tex
@@ -218,6 +218,50 @@ However, there are also assumptions that have to be made about the tool. In the
Finally, it is interesting to compare the performance of Vericert compared to existing HLS tools, to see how correctness guarantees affect the size and speed of the final hardware. This was done on a common compiler benchmark called PolyBench/C~\cite{polybench}.
+\begin{figure}
+\definecolor{polycol}{HTML}{e6ab02}
+\definecolor{polywocol}{HTML}{7570b3}
+\begin{tikzpicture}
+\begin{axis}[
+ xmode=log,
+ ymode=log,
+ height=80mm,
+ width=80mm,
+ xlabel={\legup{} execution time (ms)},
+ ylabel={\vericert{} execution time (ms)},
+ xmin=10,
+ xmax=1000000,
+ ymax=1000000,
+ ymin=10,
+ legend pos=south east,
+ %log ticks with fixed point,
+ ]
+
+
+\addplot[draw=none, mark=*, draw opacity=0, fill opacity=0.8, polycol]
+ table [x expr={\thisrow{legupcycles}/\thisrow{legupfreqMHz}}, y expr={\thisrow{vericertcycles}/\thisrow{vericertoldfreqMHz}}, col sep=comma]
+ {results/poly.csv};
+
+\addlegendentry{PolyBench}
+
+\addplot[draw=none, mark=o, fill opacity=0, polywocol]
+ table [x expr={\thisrow{legupcycles}/\thisrow{legupfreqMHz}}, y expr={\thisrow{vericertcycles}/\thisrow{vericertfreqMHz}}, col sep=comma]
+ {results/poly.csv};
+
+\addlegendentry{PolyBench w/o division}
+
+\addplot[dotted, domain=10:1000000]{x};
+%\addplot[dashed, domain=10:10000]{9.02*x + 442};
+
+\end{axis}
+\end{tikzpicture}
+\caption{A comparison of the execution time of hardware designs generated by \vericert{} and by \legup{}. \YH{Need to update performance figures.}}\label{fig:comparison_time}
+\end{figure}
+
+\section{Improvements to \vericert{}}
+
+
+
%% Acknowledgments
%\begin{acks}%% acks environment is optional
%% contents suppressed with 'anonymous'