summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--main.tex4
1 files changed, 2 insertions, 2 deletions
diff --git a/main.tex b/main.tex
index 31ff380..2c7620e 100644
--- a/main.tex
+++ b/main.tex
@@ -218,7 +218,7 @@ However, there are also assumptions that have to be made about the tool. In the
\section{Performance of such a tool}
-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}.
+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}
@@ -262,7 +262,7 @@ Finally, it is interesting to compare the performance of Vericert compared to ex
\section{Improvements to \vericert{}}
-There are many optimisations that need to be added to Vericert to make turn it into a viable and competitive HLS tool. First of all, the most important addition is a good scheduling implementation, which supports operation chaining and properly pipelining operators.
+There are many optimisations that need to be added to \vericert{} to make turn it into a viable and competitive HLS tool. First of all, the most important addition is a good scheduling implementation, which supports operation chaining and properly pipelining operators.
%% Acknowledgments
%\begin{acks}%% acks environment is optional