-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Wasm][post-MVP] Memory64 support #94108
Comments
Tagging subscribers to this area: @dotnet/area-system-memory Issue DetailsBrowsers are commonly supporting the Memory 64 specification, and it would be useful to have .NET support this as well. Apps are getting larger, and it's becoming more common to hit memory limits. Having 64 bits support would be very useful!
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsBrowsers are commonly supporting the Memory 64 specification, and it would be useful to have .NET support this as well. Apps are getting larger, and it's becoming more common to hit memory limits. Having 64 bits support would be very useful!
|
@jeromelaban we'll take a look but this is low priority for us at the moment. If you have a particular use case let us know. |
Also as @kg loves to remind me, Android Chrome is still a 32-bit app |
It looks like memory64 is starting to be shipped in browsers: WebAssembly/website#413 and the |
Browsers are commonly supporting the Memory 64 specification, and it would be useful to have .NET support this as well.
Apps are getting larger, and it's becoming more common to hit memory limits. Having 64 bits support would be very useful!
The text was updated successfully, but these errors were encountered: