Only large objects can span a 256Mbyte boundary, so an alternative
implementation would fix large-object allocation to reject allocations that
span
such a boundary. In this scenario you would not need to reserve code space
up
front and there would be n 256Mbyte limit on code size?
https://codereview.chromium.org/1147503002/
--
--
v8-dev mailing list
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
