refactor: retrieve immediates in new backend #2251
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
abrown
commented
Oct 1, 2020
github-actions
bot
added
cranelift
Subscribe to Label Actioncc @bnjbvr
This issue or pull request has been labeled: "cranelift", "cranelift:area:aarch64", "cranelift:area:machinst", "cranelift:area:x64"
Thus the following users have been cc'd because of the following labels:
To subscribe or unsubscribe from this label, edit the |
cfallin
approved these changes
Oct 1, 2020
abrown
force-pushed
the
access-immediates
branch
3 times, most recently
from
e78d0bb to
9b8c84b
Compare
bjorn3
reviewed
Oct 1, 2020
This is no change to functionality; the move is necessary in order to return InstructionData immediates in a structure way (see next commit).
This change abstracts away (from the perspective of the new backend) how immediate values are stored in InstructionData. It gathers large immediates from necessary places (e.g. constant pool) and delegates to `InstructionData::imm_value` for the rest. This refactor only touches original users of `LowerCtx::get_immediate` but a future change could do the same for any place the new backend is accessing InstructionData directly to retrieve immediates.
abrown
added a commit
to abrown/wasmtime
that referenced
this pull request
Oct 7, 2020
As discussed in bytecodealliance#2251, in order to be very confident that NaN signaling bits are correctly handled by the compiler, this switches `DataValue` to use Cranelift's `Ieee32` and `Ieee64` structures. This makes it a bit more inconvenient to interpreter Cranelift FP operations but this should change to something like `rustc_apfloat` in the future.
abrown
force-pushed
the
access-immediates
branch
from
9b8c84b to
c7aac34
Compare
abrown
commented
Oct 7, 2020
As discussed in bytecodealliance#2251, in order to be very confident that NaN signaling bits are correctly handled by the compiler, this switches `DataValue` to use Cranelift's `Ieee32` and `Ieee64` structures. This makes it a bit more inconvenient to interpreter Cranelift FP operations but this should change to something like `rustc_apfloat` in the future.
abrown
force-pushed
the
access-immediates
branch
from
c7aac34 to
3c0fe89
Compare
cfallin
pushed a commit
that referenced
this pull request
Nov 30, 2020
As discussed in #2251, in order to be very confident that NaN signaling bits are correctly handled by the compiler, this switches `DataValue` to use Cranelift's `Ieee32` and `Ieee64` structures. This makes it a bit more inconvenient to interpreter Cranelift FP operations but this should change to something like `rustc_apfloat` in the future.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
@cfallin, here is what I came up with after we discussed this last week. This change:
DataValueinto cranelift-codegen so that I can use it as a value wrapperInstructionDatathe ability to find immediate values in the format structuresLowerCtx::get_immediateto grab the value from the instruction (and the DataFlowGraph for vector immediates)I felt like this approach provides the new backend a more abstract view of immediates instead of munging directly in the
InstructionDatabut I didn't perform the refactor on the rest of the places the new backend grabs immediates because I wanted to get some feedback first.