diff options
author | Yann Herklotz <git@yannherklotz.com> | 2023-05-11 19:38:03 +0100 |
---|---|---|
committer | Yann Herklotz <git@yannherklotz.com> | 2023-05-11 19:38:03 +0100 |
commit | 47c1289ff658a5aec71635d79ffe30bb29a07876 (patch) | |
tree | 56cf6b959e37fed88c492d34defd3d7ec40e7148 /content/zettel/1c5d.md | |
parent | fbe0fc62120348f582dc4db2b614078943d0764b (diff) | |
download | zk-web-47c1289ff658a5aec71635d79ffe30bb29a07876.tar.gz zk-web-47c1289ff658a5aec71635d79ffe30bb29a07876.zip |
Add content
Diffstat (limited to 'content/zettel/1c5d.md')
-rw-r--r-- | content/zettel/1c5d.md | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/content/zettel/1c5d.md b/content/zettel/1c5d.md new file mode 100644 index 0000000..c69012e --- /dev/null +++ b/content/zettel/1c5d.md @@ -0,0 +1,19 @@ ++++ +title = "Before or after scheduling" +author = "Yann Herklotz" +tags = [] +categories = [] +backlinks = ["1c5c"] +forwardlinks = ["1c5e"] +zettelid = "1c5d" ++++ + +Register allocation is a tricky optimisation to get right, because there +are a lot of trade-offs on where to place the optimisation. Especially +in high-level synthesis, it's tricky to know where to place these, as +one can target really any architecture. + +In high-level synthesis particularly, it seems like it would be better +to perform the optimisation after scheduling, as one would want as much +freedom for scheduling as possible. This is to get the largest possible +instruction level parallelism. |