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

Only warn if needed #4749

Merged
merged 1 commit into from
Jun 11, 2024
Merged

Only warn if needed #4749

merged 1 commit into from
Jun 11, 2024

Conversation

john-sharratt
Copy link
Contributor

This patch will suppress the stack corruption warnings if asyncify is not used and hence its not a problem. This is to prevent all the large number of warnings that are being generated.

@john-sharratt john-sharratt force-pushed the only-warn-if-needed branch from dcded84 to 30514ee Compare May 26, 2024 01:11
@Arshia001
Copy link
Member

I was thinking of implementing the same thing. I was going to check for the asyncify exports instead. Indeed, it's possible to have a WASIX module that hasn't had the asyncify pass performed on it and can't ever unwind. I guess the best course of action would be to check for both the asyncify exports and the wasix imports?

@theduke
Copy link
Contributor

theduke commented May 26, 2024

Somewhat agree with both sides here:

  • if we warning is sensible, then we should only skip it if no asyncify is ever done
  • but, we might want to downgrade from a warning to some other trace

@syrusakbary syrusakbary merged commit d138752 into main Jun 11, 2024
61 checks passed
@syrusakbary syrusakbary deleted the only-warn-if-needed branch June 11, 2024 13:36
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.

4 participants