-
Notifications
You must be signed in to change notification settings - Fork 15
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
Parsing and validation of atomic instructions. #466
Conversation
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.
Thanks! Looks good so far. I didn't review in details though, I'll do so once it's closer to mergeable.
I'm not sure what's the best solution for the tests is. I think the simplest (I think that's what I did in my dev branch when I wrote the interpreter initially), is to add #[ignore]
on the tests that fail, like atomic
, and just remove the #[ignore]
locally to know where you are, and remove it definitely once the full test passes. This way you don't need to modify the tests and can use them directly from the wasm/threads repo. You can always modify them there locally for testing purposes.
I've merge #467 which let's you write |
Co-authored-by: Julien Cretin <cretin@google.com>
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.
I didn't review in details because the PR is not up-to-date with the branch (let's merge the submodule PR first). Once done, I'll do a thorough review. But from a quick glance over the PR I'd say the overall approach is sound, so it's just about me checking the spec on one side and the PR on the other.
…into wasm-threads
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.
Thanks! It seems almost there.
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.
Thanks!
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.
Thanks! Looks good enough to merge. The details can be handled when we'll merge this branch into main.
The changelog test is a bit noisy for a dev branch, let me remove it in #479. |
I've resolved the comments, but 2 things you could do in
|
Looking for early feedback on general direction, content and style. Thank you.