You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While being able to support 4GB heap sizes (as opposed to just 2GB) may not strictly be a Wasm spec thing, but a property of the external VM, it would be very useful to have 4GB heap size support dotted down in
to list which browsers/environments are capable of supporting up to 4GB Memories/Typed Arrays. That would help planning when Emscripten users should be looking to migrate to targeting 4GB heap support, for example.
The text was updated successfully, but these errors were encountered:
@dschuff just said the following: "[T]his would have been a good idea in 2020. All the browsers have had support for quite a while now". So I guess it's fine to just close this. Sorry for not acting upon this when it was more of an open question.
While being able to support 4GB heap sizes (as opposed to just 2GB) may not strictly be a Wasm spec thing, but a property of the external VM, it would be very useful to have 4GB heap size support dotted down in
https://webassembly.org/roadmap/
to list which browsers/environments are capable of supporting up to 4GB Memories/Typed Arrays. That would help planning when Emscripten users should be looking to migrate to targeting 4GB heap support, for example.
The text was updated successfully, but these errors were encountered: