summaryrefslogtreecommitdiffstats
path: root/content/zettel/1c10.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/1c10.md
parentfbe0fc62120348f582dc4db2b614078943d0764b (diff)
downloadzk-web-47c1289ff658a5aec71635d79ffe30bb29a07876.tar.gz
zk-web-47c1289ff658a5aec71635d79ffe30bb29a07876.zip
Add content
Diffstat (limited to 'content/zettel/1c10.md')
-rw-r--r--content/zettel/1c10.md14
1 files changed, 14 insertions, 0 deletions
diff --git a/content/zettel/1c10.md b/content/zettel/1c10.md
new file mode 100644
index 0000000..1f67276
--- /dev/null
+++ b/content/zettel/1c10.md
@@ -0,0 +1,14 @@
++++
+title = "Abstract Interpretation of Hardware"
+author = "Yann Herklotz"
+tags = []
+categories = []
+backlinks = ["1c9"]
+forwardlinks = []
+zettelid = "1c10"
++++
+
+It would be nice to be able to interpret hardware abstractly to compare
+it to code that generated it. However, this seems infeasible because at
+each iteration the whole hardware gets evaluated, and all the registers
+might change again.