Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
aarch64: Migrate {s,u}{div,rem} to ISLE #3572
aarch64: Migrate {s,u}{div,rem} to ISLE #3572
Changes from all commits
8fff710
83b6108
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Just a drive-by comment (I'm happy to review the whole thing too but wanted to note this first): eek, a language wart appears! I had included
#t
and#f
bool constants (Scheme-style) but they lower to1
/0
(i.e., integers); this is largely because the DSL compiler's IR hasConstInt
but notConstBool
because... no good reason. I see here you've used the$
syntax to just pass throughfalse
as an opaque constant name; that works but we should really fix this.(Outside the scope of this PR obviously, just noting -- I'll file an issue for it. Sorry about this!)
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.
Ah ok! I'm happy to switch to whatever is the right way to do this, I think there's other places that stem from
wasmtime/cranelift/codegen/src/prelude.isle
Lines 13 to 14 in 0580c84
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.
Filed #3573 for this, happy to do the cleanup later; this bit can land as-is for now :-)
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.
Should
CondBrKind
be moved into ISLE? This seems like a lot of code to write to glue the non-ISLE definition in with the ISLE code. Doesn't need to happen in this PR (or at all) unless you want, but just something I though of when looking at this code.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.
Currently
CondBrKind
is pretty heavily used it looks like in the backend and since ISLE can only generate named-field enums instead of tuple-enums likeCondBrKind
is today I think I'll leave it defined externally, but I agree this'd be a good future cleanup!