Comment #6 on issue 2790 by [email protected]: Sparse array
constructor gives "illegal access" at 98297 elements and beyond
http://code.google.com/p/v8/issues/detail?id=2790
Unfortunately a simple fall-back to LO-space will not solve the problem
completely. If the HAllocate requests allocation in new-space (i.e.
ALLOCATE_IN_NEW_SPACE), then the object _must_ be allocated in new-space.
Subsequent instructions (e.g. HStoreNamedField) depend on this fact and
might remove write-barriers. The only quick-fix that I can think of right
now, is to deopt if the size exceeds new-space boundaries. But that would
introduce another deopt-loop where we don't learn new information from a
deopt.
--
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/groups/opt_out.
