Skip to content

[34.0.0] Revert "Stack switching: Infrastructure and runtime support" #10938

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jun 5, 2025
Merged

[34.0.0] Revert "Stack switching: Infrastructure and runtime support" #10938

merged 1 commit into from
Jun 5, 2025

Conversation

alexcrichton
Copy link
Member

This is a revert of #10388 for the 34.0.0 release branch. That commit was the last commit in on the release branch and there should be no harm in deferring it for one extra release (stack-switching is still a work-in-progress on main) and the hope is that this reduces the risk/need to backport any changes.

@alexcrichton alexcrichton requested review from a team as code owners June 5, 2025 21:54
@alexcrichton alexcrichton requested review from fitzgen and removed request for a team June 5, 2025 21:54
@alexcrichton alexcrichton merged commit a7d3300 into bytecodealliance:release-34.0.0 Jun 5, 2025
160 checks passed
@alexcrichton alexcrichton deleted the backport branch June 5, 2025 22:22
@alexcrichton
Copy link
Member Author

cc @posborne sorry I should have cc'd you on this to start. I'm not dead-set on doing this I just figured it'd be a reasonable idea. If you would prefer to get this infrastructure landed on the release branch though I think it'd be reasonable to re-land. (and to clarify I have no intention of reverting on main, this was just to de-risk the release branch a little)

@posborne
Copy link
Collaborator

posborne commented Jun 6, 2025

cc @posborne sorry I should have cc'd you on this to start. I'm not dead-set on doing this I just figured it'd be a reasonable idea. If you would prefer to get this infrastructure landed on the release branch though I think it'd be reasonable to re-land. (and to clarify I have no intention of reverting on main, this was just to de-risk the release branch a little)

No, I'm happy with this not being included on the release branch for this cycle.

@alexcrichton alexcrichton mentioned this pull request Jul 7, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fitzgen fitzgen fitzgen approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@alexcrichton @posborne @fitzgen