diff options
author | Yann Herklotz <git@yannherklotz.com> | 2021-02-24 14:17:41 +0000 |
---|---|---|
committer | Yann Herklotz <git@yannherklotz.com> | 2021-02-24 14:17:41 +0000 |
commit | 4adae918a6f4c2cb529abdba6af2fcaa1b570b1f (patch) | |
tree | aa4f550037c1da2de9b59233bdea78c4668e3cb9 | |
parent | 004b22ea997f4a5b04a06b9b40c3cdea23c455a9 (diff) | |
download | latte21_hlstpc-4adae918a6f4c2cb529abdba6af2fcaa1b570b1f.tar.gz latte21_hlstpc-4adae918a6f4c2cb529abdba6af2fcaa1b570b1f.zip |
Add information about performance
-rw-r--r-- | main.tex | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -214,6 +214,8 @@ However, \citet{du21_fuzzin_high_level_synth_tools}, for example, show that on a \subsection{Will the generated designs be fast enough?} +Another concern might be that a verified HLS tool might not be performant enough to be usable in practice. If that is the case, then the verification effort could be seen as useless + \subsection{A Verified tool can still be flaky and fail} It is true that a verified tool is still allowed to fail at compilation time, meaning none of the correctness proofs need to hold, as no output was produced. However, this is only a matter of putting more engineering work into the tool to make it reliable. If a test bench is available, it is also quite simple to check this property, as it just has to be randomly tested without even having to execute the output. |