Skip to content
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.

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

[Parser] Parse local.set and global.set of tuple values correctly #6250

Merged
merged 2 commits into from
Jan 30, 2024

Conversation

tlively
Copy link
Member

@tlively tlively commented Jan 26, 2024

These instructions always pop a single value, except when tuples are involved,
in which case they need special handling to know how many values to pop.

@tlively
Copy link
Member Author

tlively commented Jan 26, 2024

@tlively
Copy link
Member Author

tlively commented Jan 29, 2024

Merge activity

  • Jan 29, 6:36 PM: @tlively started a stack merge that includes this pull request via Graphite.
  • Jan 29, 6:37 PM: Graphite rebased this pull request as part of a merge.
  • Jan 29, 7:03 PM: @tlively merged this pull request with Graphite.

Base automatically changed from parser-tuple-types to main January 29, 2024 23:36
These instructions always pop a single value, except when tuples are involved,
in which case they need special handling to know how many values to pop.
@tlively tlively merged commit c0046ad into main Jan 30, 2024
15 checks passed
@tlively tlively deleted the parser-tuple-sets branch January 30, 2024 00:03
radekdoulik pushed a commit to dotnet/binaryen that referenced this pull request Jul 12, 2024
…bAssembly#6250)

These instructions always pop a single value, except when tuples are involved,
in which case they need special handling to know how many values to pop.
@gkdn gkdn mentioned this pull request Aug 31, 2024
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