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

Memory management #177

Closed
penzn opened this issue Nov 7, 2018 · 3 comments
Closed

Memory management #177

penzn opened this issue Nov 7, 2018 · 3 comments

Comments

@penzn
Copy link
Collaborator

penzn commented Nov 7, 2018

Sharing linear memory between WASM and JavaScript without shared memory management is slightly hazardous -- one side can easily clobber what the other wrote. It would be beneficial to provide C memory management functionality in wasm libc, that can be used for both JS and WebAssembly, similar to what Rust does.

@penzn
Copy link
Collaborator Author

penzn commented Nov 16, 2018

Ping @sunfishcode

@sunfishcode
Copy link
Member

I think tools that ease the interop between JS and wasm are outside the scope of reference-sysroot.

One thing that should significantly help in this area is the host bindings proposal. That will allow one to pass a slice of linear memory to a function, rather than just exporting all of memory.

@sunfishcode
Copy link
Member

Host bindings has evolved into WebIDL bindings which is evolving further and aiming to be not specific to the Web. It's an ongoing story, but that's where I expect this issue will be solved, rather than in reference-sysroot.

@sunfishcode sunfishcode transferred this issue from WebAssembly/wasi-libc-old Mar 3, 2020
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

No branches or pull requests

2 participants