This generally looks OK.
But as discussed offline: It currently fails a few tests because the
restriction
is tighter than it needs to be. To get a finer grained coverage we just
need to
run with Heap::DisableInlineAllocation() turned on and we will get better
assertion checking at the actual place of allocation.
https://codereview.chromium.org/196533007/
--
--
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.
