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.

Sign up for GitHub

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

Jump to bottom

wasm2c: Split size and capacity #2329

Open
SoniEx2 opened this issue Nov 15, 2023 · 0 comments
Open

wasm2c: Split size and capacity #2329

SoniEx2 opened this issue Nov 15, 2023 · 0 comments

Comments

@SoniEx2
Copy link
Contributor

SoniEx2 commented Nov 15, 2023 •
edited
Loading

wasm2c memories currently only take size into account. Splitting into size and capacity would impact threads/shared memory support (since realloc is unsound) but is also relevant for big-endian (both guard pages and shared memory). cc @shravanrn

(This also lets the runtime use more efficient memory growth strategies, if desired.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SoniEx2