Skip to content

Conversation

@tlively
Copy link
Member

@tlively tlively commented Jan 6, 2024

Since branches to loops go to the beginnings of the loops, they should send
values matching the input types for the loops (which are always none because we
don't support loop input types). IRBuilder was previously using the output types
of loops to determine what values the branches should carry, which was
incorrect. Fix it.

Since branches to loops go to the beginnings of the loops, they should values
matching the input types for the loops (which are always none because we don't
support loop input types). IRBuilder was previously using the output types of
loops to determine what values the branches should carry, which was incorrect.
Fix it.
@tlively tlively requested a review from kripken January 6, 2024 00:37
@tlively
Copy link
Member Author

tlively commented Jan 6, 2024

Current dependencies on/for this PR:

This stack of pull requests is managed by Graphite.

Copy link
Member

@kripken kripken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

they should values in description should have "send" in it?

@tlively
Copy link
Member Author

tlively commented Jan 6, 2024

Oops, yes. Fixed.

@tlively tlively merged commit c3b2f24 into main Jan 6, 2024
@tlively tlively deleted the parser-loop-labels branch January 6, 2024 01:54
radekdoulik pushed a commit to dotnet/binaryen that referenced this pull request Jul 12, 2024
Since branches to loops go to the beginnings of the loops, they should send
values matching the input types for the loops (which are always none because we
don't support loop input types). IRBuilder was previously using the output types
of loops to determine what values the branches should carry, which was
incorrect. Fix it.
@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.

3 participants