diff options
author | Yann Herklotz <git@yannherklotz.com> | 2021-02-23 16:19:18 +0000 |
---|---|---|
committer | Yann Herklotz <git@yannherklotz.com> | 2021-02-23 16:19:18 +0000 |
commit | e1b78eb48c86e2280a07906ca7f2cfaed7bf0d2c (patch) | |
tree | d519e3246d78c1c7bb31ef54d8a8ba4deb2c0deb | |
parent | 89539c44c030101bfe73917716c255672081f485 (diff) | |
download | latte21_hlstpc-e1b78eb48c86e2280a07906ca7f2cfaed7bf0d2c.tar.gz latte21_hlstpc-e1b78eb48c86e2280a07906ca7f2cfaed7bf0d2c.zip |
Add better formatting
-rw-r--r-- | main.tex | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -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 |