Skip to content

Release 47.0.0 alias region backports#13826

Merged
alexcrichton merged 3 commits into
bytecodealliance:release-47.0.0from
fitzgen:release-47.0.0-alias-region-backports
Jul 6, 2026
Merged

Release 47.0.0 alias region backports#13826
alexcrichton merged 3 commits into
bytecodealliance:release-47.0.0from
fitzgen:release-47.0.0-alias-region-backports

Conversation

@fitzgen

@fitzgen fitzgen commented Jul 6, 2026

Copy link
Copy Markdown
Member

fitzgen and others added 3 commits July 6, 2026 02:56
This also bumped the AliasRegionKey's kind bits up to 6, which triggered a mass
renumbering in the disas tests.
…ealliance#13825)

We should never emit a load/store instruction that isn't tagged with an alias
region.
…iance#13823)

This commit fixes a minor mistake to use the right alias region when
initializing a passive element segment during startup. This requires
using a slightly different helper than was previously done for GC
references because the element segment lives in a different region than
the default GC heap.
@fitzgen fitzgen requested review from a team as code owners July 6, 2026 19:07
@fitzgen fitzgen requested review from alexcrichton and removed request for a team July 6, 2026 19:07
@alexcrichton alexcrichton merged commit d106f4b into bytecodealliance:release-47.0.0 Jul 6, 2026
196 checks passed
@fitzgen fitzgen deleted the release-47.0.0-alias-region-backports branch July 6, 2026 19:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants