[BLOG POST] C++ infra for bril #428
Conversation
There was a problem hiding this comment.
Hello! Congratulations on finishing your project. This blog post needs some more details on your design decisions. I have left several markers where your high-level summaries could be backed up with concrete examples and detail. Surely there are interesting, specific outcomes that you can report here.
content/blog/2023-12-11-BrilCpp.md
Outdated
|
|
||
| We found a few memory leaks with our final iteration but our program should still be memory safe. | ||
|
|
||
| For runtime performance, we ran the existing `brili` interpreter as well as our own interpreter against the core benchmarks in the course repo. We timed the wall clock runtime of both our interpreter and the existing interpreter over all benchmarks in the folder. We observe that we can obtain upwards of 10x improvement over the previous benchmark in wall clock runtime for some of the benchmarks. . |
There was a problem hiding this comment.
It's too bad that you didn't get a chance to compare against the existing fast interpreter, written in Rust. That would have been a more instructive comparison; comparing against an implementation sitting on top of a JIT mostly just measures startup time.
|
Looks like the Zola CI is complaining about missing "front matter." You can see a description of what is required in this repo's README: |
with xalbt
C++ infra for bril
repo
Closes #404