diff options
| author | John Wickerson <j.wickerson@imperial.ac.uk> | 2020-09-14 21:46:19 +0000 |
|---|---|---|
| committer | overleaf <overleaf@localhost> | 2020-09-14 21:46:22 +0000 |
| commit | 114f25e953f0a417ba36803c3eae07ec95ac8821 (patch) | |
| tree | d07ce59ba022966c9547f4e49ec43ddc1bdadb5c | |
| parent | c1f4f21fff5ae7abc9563d6083e7bfbc60332830 (diff) | |
| download | fccm21_esrhls-114f25e953f0a417ba36803c3eae07ec95ac8821.tar.gz fccm21_esrhls-114f25e953f0a417ba36803c3eae07ec95ac8821.zip | |
Update on Overleaf.
| -rw-r--r-- | conclusion.tex | 4 | ||||
| -rw-r--r-- | eval_rewrite.tex | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/conclusion.tex b/conclusion.tex index ab9b212..186fdc5 100644 --- a/conclusion.tex +++ b/conclusion.tex @@ -1,9 +1,9 @@ \section{Conclusion} We have shown how existing fuzzing tools can be modified so that their outputs are compatible with HLS tools. We have used this testing framework to run 10,000 test cases \JW{check numbers} through three different HLS tools. In total, we found at least 6 individual and unique bugs in all the tools, which have been reduced, analysed, and reported to the tool vendors. These bugs include crashes as well as instances of generated designs not behaving in the same way as the original code. -Further work could be done on supporting more HLS tools, especially ones that claim to prove that their output is correct before terminating. This could give an indication on how effective these proofs are, and how often they are actu many times they cannot prove the output equivalent. +Further work could be done on supporting more HLS tools, especially ones that claim to prove that their output is correct before terminating. This could give an indication on how effective these proofs are, and how often they are actually able to complete their equivalence proofs during compilation in a feasible time scale. -As HLS is becoming increasingly useful, it is important to make sure that these tools are also reliable. We hope that this work further motivates the design of correct HLS tools, either by validating that the output is correct or by proving the HLS tool correct. +As HLS is becoming increasingly relied upon, it is important to make sure that HLS tools are also reliable. We hope that this work further motivates the design of correct HLS tools, either by validating that the output is correct or by proving the HLS tool correct. %%% Local Variables: %%% mode: latex diff --git a/eval_rewrite.tex b/eval_rewrite.tex index 4a980ad..4ad0d5a 100644 --- a/eval_rewrite.tex +++ b/eval_rewrite.tex @@ -21,7 +21,7 @@ \node at (-7.3,1) {\Huge 162 / \textcolor{red}{6}}; \node at (-7.3,5.2) {\Huge 0 / \textcolor{red}{5}}; \node at (-7.3,3.8) {\Huge 0 / \textcolor{red}{0}}; - \node at (-13,-0.5) {\Huge 5856 / \textcolor{red}{0}}; + \node at (-13.5,-0.5) {\Huge 5856}; \end{tikzpicture} } \caption{Venn diagram showing the bug failures in each tool out of 6700 test cases that were run. Overlapping regions mean that the test cases failed in all those tools. The numbers in red represent the number of test cases that timed out after two hours.}\label{fig:existing_tools} |