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

Don't force the use of imported memory under WASM2JS #21195

Merged
merged 1 commit into from
Jan 30, 2024
Merged

Don't force the use of imported memory under WASM2JS #21195

merged 1 commit into from
Jan 30, 2024
+66 −62

Commits on Jan 29, 2024

  1. Don't force the use of imported memory under WASM2JS 

    Setting `IMPORTED_MEMORY` can have other implications and don't want t
by default just because we chose WASM2JS.

The there is a very minor code size regression here that only effects
WASM2JS, but when combined with emscripten-core#21196 the overall effect is still a
win.

See emscripten-core#21071
    @sbc100
    sbc100 committed Jan 29, 2024
    Configuration menu
    Copy the full SHA
    ba160e1 View commit details
    Browse the repository at this point in the history