summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorYann Herklotz <git@yannherklotz.com>2020-09-14 22:42:33 +0100
committerYann Herklotz <git@yannherklotz.com>2020-09-14 22:42:33 +0100
commitb8e6acf2ae98c64d4e4151eff046d50677324118 (patch)
tree125175dcad84dde37629c733d04f699f2389cf53
parent28363fbb794bbaa698ca6578c44cd268cc4afda2 (diff)
parent5bc0e6b69a0eb8fc2888743dbf60ad6a0aab029b (diff)
downloadfccm21_esrhls-b8e6acf2ae98c64d4e4151eff046d50677324118.tar.gz
fccm21_esrhls-b8e6acf2ae98c64d4e4151eff046d50677324118.zip
Merge branch 'master' of https://git.overleaf.com/5f2d21b9b10d6c0001c164a4 into master
-rw-r--r--conclusion.tex4
1 files changed, 2 insertions, 2 deletions
diff --git a/conclusion.tex b/conclusion.tex
index 92bb12f..64e77e2 100644
--- a/conclusion.tex
+++ b/conclusion.tex
@@ -1,7 +1,7 @@
\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 vendos These consisted of crashes as well as generation of designs that did not behave in the same way as the original code.
+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 prove that the output is correct before terminating. This could give an indication on how effective these proofs are, and how 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 many times they cannot prove the output equivalent.
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.