Skip to content

Conversation

@kripken
Copy link
Member

@kripken kripken commented May 30, 2024

Without that logic we could end up dropping that particular effect. This actually
made a test pass when it should not: the modified test here has a function with
effects that are ok to remove, but it had a loop which adds MayNotReturn which
we should actually not remove, so it was removed erroneously.

To fix the test, add other effects there (local ones) that we can see are removable.
Also add a function with a loop to test that we do not remove an infinite loop,
which adds coverage for the fix here.

@kripken kripken requested a review from tlively May 30, 2024 20:40
@kripken
Copy link
Member Author

kripken commented May 30, 2024

This was hard to fuzz because the effect of an infinite loop is not something we can actually execute...

@kripken kripken merged commit ea4d9e4 into WebAssembly:main Jun 3, 2024
@kripken kripken deleted the missing branch June 3, 2024 21:19
@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