mem: add an immediate offset to Load/Store ops.#44
Draft
eddyb wants to merge 7 commits intoeddyb/vectorfrom
Draft
mem: add an immediate offset to Load/Store ops.#44eddyb wants to merge 7 commits intoeddyb/vectorfrom
offset to Load/Store ops.#44eddyb wants to merge 7 commits intoeddyb/vectorfrom
Conversation
… `OpLoad`/`OpStore`.
This was referenced Apr 27, 2026
This file contains hidden or 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
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.
Note: this PR is a draft to avoid accidental merging onto its "base" branch (used as a form of ad-hoc PR stacking), and will remain as such, until its "base" branch can be set to
main, i.e. all prerequisite PRs will have landed, up to and including this PR (whose branch is the "base" of this one):Originally submitted as (description mostly copied from there):
Load/Storeops. EmbarkStudios/spirt#41While separate offseting works fine in general, having an immediate offset inside loads and stores (as this PR adds) can make the simplest case (i.e. no array indexing or buffers - especially local variables) easier.
There's two usecases that motivated this change:
qptr::lowersupport for Disaggregate by-valueOpTypeStruct/OpTypeArrayinputs/outputs. #45Op{Load,Store}would need to turn into NMemOp::{Load,Store}(one per aggregate leaf), and needing NQPtrOp::Offsets as well would be an annoying drawbackmem2reg+SROA, which specifically only propagates stores to loads, within local variables, and treats all other uses of the local variable base pointer as "escaping" (i.e. the contents of the variable can't be known anymore)TODO: changelog, maybe a comparison example (kinda hard tho).