Comment #7 on issue 3907 by [email protected]: Allowing asm.js memory
growth causes big slowdown
https://code.google.com/p/v8/issues/detail?id=3907
This illustrates the problems with this changeable heap strategy. It does
not allow a JS implementation to decide the trade-off between a fixed and
large heap versus a changeable growing heap. What should have been done is
to add support for managing the asm.js heap, allowing an application to
declare the resource usage and to work with the resources offered by the JS
implementation.
V8 might have then ignored supporting a changeable heap for now with little
loss on 64 bit implementations with lots of address space.
The Odin asm.js implementation retains the inline bounds checking and
patches these when the heap changes. The code is bloated with bounds checks
and the constraints will likely block future optimization unless a JIT is
used. Odin x64 uses memory protection to implement bounds checking,
avoiding inline bounds checks, and a signal handler emulates an oob access.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
