summaryrefslogtreecommitdiffstats
path: root/content/zettel/3c8.md
diff options
context:
space:
mode:
authorYann Herklotz <git@yannherklotz.com>2023-05-11 19:38:03 +0100
committerYann Herklotz <git@yannherklotz.com>2023-05-11 19:38:03 +0100
commit47c1289ff658a5aec71635d79ffe30bb29a07876 (patch)
tree56cf6b959e37fed88c492d34defd3d7ec40e7148 /content/zettel/3c8.md
parentfbe0fc62120348f582dc4db2b614078943d0764b (diff)
downloadzk-web-47c1289ff658a5aec71635d79ffe30bb29a07876.tar.gz
zk-web-47c1289ff658a5aec71635d79ffe30bb29a07876.zip
Add content
Diffstat (limited to 'content/zettel/3c8.md')
-rw-r--r--content/zettel/3c8.md26
1 files changed, 26 insertions, 0 deletions
diff --git a/content/zettel/3c8.md b/content/zettel/3c8.md
new file mode 100644
index 0000000..76cad56
--- /dev/null
+++ b/content/zettel/3c8.md
@@ -0,0 +1,26 @@
++++
+title = "Verifying Stability Conditions on HLS"
+date = "2022-10-04"
+author = "Yann Herklotz"
+tags = []
+categories = []
+backlinks = ["3c7"]
+forwardlinks = ["3c8a"]
+zettelid = "3c8"
++++
+
+Currently, the correctness proof for HLS only takes into account the
+actual correctness of the final result that is computed. Instead, it
+would be useful to also have a notion of stability of the output. This
+means that changes in the input to a different, equivalent program
+should not result in a large difference in the design of the output.
+However, even there, there are two possibilities:
+
+- Stability of performance metrics, such as latency, throughput and
+ area.
+- Stability of architecture, which implies the above but may be
+ restrictive.
+
+It might be easiest to start by proving stability of the architecture
+and see how restrictive that metric is, and how many optimisations do
+not actually have that property.