Wasmtime GitHub notifications bot (Dec 14 2021 at 15:03): Wasmtime GitHub notifications bot (Dec 14 2021 at 15:03):alexcrichton opened PR #3600 from isle-5-uextend-sextend to main:
This commit migrates the sign/zero extension instructions from
lower_inst.rsto ISLE. There's actually a fair amount going on in this
migration since a few other pieces needed touching up along the way as
well:
First is the actual migration of
uextendandsextend. These
instructions are relatively simple but end up having a number of special
cases. I've attempted to replicate all the cases here but
double-checks would be good.This commit actually fixes a few issues where if the result of a vector
extraction is sign/zero-extended into i128 that actually results in
panics in the current backend.This commit adds exhaustive testing for
extension-of-a-vector-extraction is a noop wrt extraction.A bugfix around ISLE glue was required to get this commit working,
notably the case where theRegMapperimplementation was trying to
map an input to an output (meaning ISLE was passing through an input
unmodified to the output) wasn't working. This requires amov
instruction to be generated and this commit updates the glue to do
this. At the same time this commit updates the ISLE glue to share more
infrastructure between x64 and aarch64 so both backends get this fix
instead of just aarch64.Overall I think that the translation to ISLE was a net benefit for these
instructions. It's relatively obvious what all the cases are now unlike
before where it took a few reads of the code and some boolean switches
to figure out which path was taken for each flavor of input. I think
there's still possible improvements here where, for example, the
put_in_reg_{s,z}ext64helper doesn't use this logic so technically
those helpers could also pattern match the "well atomic loads and vector
extractions automatically do this for us" but that's a possible future
improvement for later (and shouldn't be too too hard with some ISLE
refactoring).<!--
Please ensure that the following steps are all taken care of before submitting
the PR.
[ ] This has been discussed in issue #..., or if not, please tell us why
here.[ ] A short description of what this does, why it is needed; if the
description becomes long, the matter should probably be discussed in an issue
first.[ ] This PR contains test cases, if meaningful.
- [ ] A reviewer from the core maintainer team has been assigned for this PR.
If you don't know who could review this, please indicate so. The list of
suggested reviewers on the right can help you.Please ensure all communication adheres to the code of conduct.
-->
Wasmtime GitHub notifications bot (Dec 14 2021 at 15:03):alexcrichton requested fitzgen for a review on PR #3600.
Wasmtime GitHub notifications bot (Dec 14 2021 at 21:51):fitzgen submitted PR review.
Wasmtime GitHub notifications bot (Dec 14 2021 at 21:51):fitzgen merged PR #3600.
Last updated: Nov 22 2024 at 16:03 UTC