-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Queued cranelift-fuzzgen enhancements #4798
Comments
akirilov-arm
added
cranelift
Issues related to the Cranelift code generator
fuzzing
Issues related to our fuzzing infrastructure
labels
Sep 2, 2022
Subscribe to Label Actioncc @fitzgen
This issue or pull request has been labeled: "fuzzing"
Thus the following users have been cc'd because of the following labels:
To subscribe or unsubscribe from this label, edit the |
...I guess I should close this since all the PRs I was tracking are merged now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We got a large batch of new fuzz-bugs from cranelift-fuzzgen (and cranelift-icache) this week. Some of them are bugs we don't want to fix yet because they're just x64 lowerings that aren't implemented yet, or things that we do want to test eventually but haven't built all the testing infrastructure for yet. We're trying to make sure that all the bugs we do want to fix are fully dealt with before we start changing fuzzing input formats and invalidating our current test cases.
Check off these issues once they are addressed by either an already-merged fix, or by a pending PR that we aren't ready to merge yet:
(left == right)
" #4755Option::unwrap()
on aNone
value #4770And these are the PRs that we need to merge when we're satisfied with our investigations of the above issues:
I think we're ready to merge these. @afonso360 and @cfallin, do you agree?
The text was updated successfully, but these errors were encountered: