diff options
| author | John Wickerson <j.wickerson@imperial.ac.uk> | 2021-09-10 14:00:17 +0000 |
|---|---|---|
| committer | node <node@git-bridge-prod-0> | 2021-09-10 14:17:12 +0000 |
| commit | 23d94e9aa9b54e6f24097d2fbbf8da55a9679ee4 (patch) | |
| tree | fb430e640822afc263e1338dbe90a2b1b05c7aa4 /introduction.tex | |
| parent | c7f22722573261a20221de144b7b93b8e46ee01b (diff) | |
| download | oopsla21_fvhls-23d94e9aa9b54e6f24097d2fbbf8da55a9679ee4.tar.gz oopsla21_fvhls-23d94e9aa9b54e6f24097d2fbbf8da55a9679ee4.zip | |
Update on Overleaf.
Diffstat (limited to 'introduction.tex')
| -rw-r--r-- | introduction.tex | 12 |
1 files changed, 3 insertions, 9 deletions
diff --git a/introduction.tex b/introduction.tex index abf6271..1871a26 100644 --- a/introduction.tex +++ b/introduction.tex @@ -51,15 +51,9 @@ The contributions of this paper are as follows: \item In Section~\ref{sec:evaluation}, we evaluate \vericert{} on the \polybench{} benchmark suite~\cite{polybench}, and compare the performance of our generated hardware against an existing, unverified HLS tool called \legup{}~\cite{canis11_legup}. We show that \vericert{} generates hardware that is \slowdownOrig$\times$ slower (\slowdownDiv$\times$ slower in the absence of division) and \areaIncr$\times$ larger than that generated by \legup{}. This performance gap can be largely attributed to \vericert{}'s current lack of support for instruction-level parallelism and the absence of an efficient, pipelined division operator. We intend to close this gap in the future by introducing (and verifying) HLS optimisations of our own, such as scheduling and memory analysis. This section also reports on our campaign to fuzz-test \vericert{} using over a hundred thousand random C programs generated by Csmith~\cite{yang11_findin_under_bugs_c_compil} in order to confirm that its correctness theorem is watertight. %\NR{Question rather than comment: Will there be verification issues to add support for hard IPs like division blocks?}\YH{Not really any issues, just many different levels of reliability. You don't have to prove IP correct, but theoretically could.} \end{itemize} %\JW{This sentence seems pretty good to me; is it up-to-date with the latest `challenges' you've faced?} -\vericert{} is fully open source and available online~\cite{yann_herklotz_2021_5093839}. - -\begin{center} -\ifANONYMOUS -[GitHub link removed for blind review] -\else -\url{https://github.com/ymherklotz/vericert} -\fi -\end{center} + +\paragraph{Companion material} +\vericert{} is fully open source and available on GitHub at \url{https://github.com/ymherklotz/vericert}. A snapshot of the \vericert{} development is also available in a Zenodo repository~\cite{yann_herklotz_2021_5093839}, which also contains \JW{fill this in}. %%% Local Variables: |