-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
waffle: initial Bytecode Alliance-hosted version. #1
Conversation
Support irreducible control flow by converting it to reducible control flow.
This avoids crashing on very long function bodies.
…mmand. "Every Wasm compiler library contains an incomplete, bug-ridden implementation of half of wasip1", the saying goes. (Or was that about Lisp implementations?) Let's remove the very hacky implementation here: it was only useful to debug waffle during bringup but shouldn't really exist as a user-facing functionality at this point.
This was useful to help debugging at one point, especially differential comparison of before- and after-transform function bodies, but it's an awkward way of doing it (with a new kind of value definition in the IR) and is largely unused at this point, so let's remove it.
For the record: once this is reviewed and merged, my plan is to make another release right away, so the "pipeline is flushed" and all published artifacts come from the new official repo. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall this looks great!
Thanks for the review/feedback; updated! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
This PR imports the entire commit history of waffle (almost three years of it!) into the bytecodealliance/waffle repository1.
A small amount of the code this includes has already been reviewed in PRs in my initial repo (cfallin/waffle), but most has not. Let's fix that!
Footnotes
technical note: I wanted to keep the full commit history (including a few contributions from others I've gotten in the past). GitHub by default doesn't allow a PR to suggest replacing the
main
branch with an unrelated commit, though, and rebasing everything on top of Nick's "empty" initial commit created with this repo was proving challenging with nonlinear history. The best methodology I was able to come with was to create a final merge-commit between my repo's head and this empty initial-commit; thus the history has two roots, but GitHub is happy to see the trees are "related". ↩