summaryrefslogtreecommitdiffstats
path: root/content/zettel/3c3h3.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/zettel/3c3h3.md')
-rw-r--r--content/zettel/3c3h3.md20
1 files changed, 20 insertions, 0 deletions
diff --git a/content/zettel/3c3h3.md b/content/zettel/3c3h3.md
new file mode 100644
index 0000000..00710ce
--- /dev/null
+++ b/content/zettel/3c3h3.md
@@ -0,0 +1,20 @@
++++
+title = "Implementing superblock scheduling in Vericert"
+author = "Yann Herklotz"
+tags = []
+categories = []
+backlinks = ["3c3h2"]
+forwardlinks = ["3c3h4"]
+zettelid = "3c3h3"
++++
+
+The other way one could compare hyperblock scheduling and superblock
+scheduling, with a focus on how they compare in HLS specifically, would
+be to take the superblock scheduling and implement it inside of
+Vericert. However, the main problem is that CompCert-KVX is a heavily
+modified version of CompCert, and therefore cannot be integrated easily
+into CompCert itself on it's own. In addition to that, trying to compile
+Vericert only with CompCert-KVX runs into more issues, mainly being that
+Vericert uses the x86 backend in CompCert, whereas CompCert-KVX has only
+implemented the riscV, aarch64 and KVX back ends for superblock
+scheduling.