Skip to content

fix: use _malloc/_free to allocate memory in setMemory #5625

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

Closed
wants to merge 5 commits into from

Conversation

mnater
Copy link
Contributor

@mnater mnater commented Apr 4, 2023

see issue #5595

@mnater mnater changed the title feat: optionally change stack size fix: use _malloc/_free to allocate memory in setMemory Apr 5, 2023
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.

malloc/free looks good!

Please remove the other changes, though - I don't think we need to make the stack size customizable now. (And it has a downside as it bakes 64K as the default, rather than deferring to emscripten to set the default.)

@mnater
Copy link
Contributor Author

mnater commented Apr 7, 2023

I don't know a clean way to remove the older commits. 🤷‍♂️
I'll close this PR and send a new one.

@mnater mnater closed this Apr 7, 2023
mnater added a commit to mnater/binaryen that referenced this pull request Apr 7, 2023
@mnater
Copy link
Contributor Author

mnater commented Apr 7, 2023

#5646

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