summaryrefslogtreecommitdiffstats
path: root/content/zettel/1f4b.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/zettel/1f4b.md')
-rw-r--r--content/zettel/1f4b.md20
1 files changed, 20 insertions, 0 deletions
diff --git a/content/zettel/1f4b.md b/content/zettel/1f4b.md
new file mode 100644
index 0000000..1ffd459
--- /dev/null
+++ b/content/zettel/1f4b.md
@@ -0,0 +1,20 @@
++++
+title = "Fuzz testing predictability of HLS tools"
+author = "Yann Herklotz"
+tags = []
+categories = []
+backlinks = ["1f4a"]
+forwardlinks = ["1f4a"]
+zettelid = "1f4b"
++++
+
+One this note, one might be able to fuzz-test the predictability of HLS
+tools. One simple property that one might want to show always hold is
+the one noted in ([\#1f4a]). This could be done by adding dead-code to
+hardware designs or input to HLS tools, and noting if the HLS tool ever
+manage to optimise the hardware more due to these changes. This should
+not happen if the HLS tools should be predictable, because that means
+that adding random dead-code could actually lead to better designs, even
+though the HLS should be designing that hardware in the first place.
+
+ [\#1f4a]: /zettel/1f4a