https://codereview.chromium.org/880043003/diff/20001/test/cctest/test-unboxed-doubles.cc
File test/cctest/test-unboxed-doubles.cc (right):
https://codereview.chromium.org/880043003/diff/20001/test/cctest/test-unboxed-doubles.cc#newcode1237
test/cctest/test-unboxed-doubles.cc:1237: // Increase the chance of
'bump-the-pointer' allocation in old space.
On 2015/02/02 21:00:54, Hannes Payer wrote:
I do not get this line. Why does that increase the chance of
bump-pointer
allocation?
Sorry, that was a copy/paste. Done.
https://codereview.chromium.org/880043003/diff/20001/test/cctest/test-unboxed-doubles.cc#newcode1270
test/cctest/test-unboxed-doubles.cc:1270: while ((*limit_addr -
*top_addr) > allocation_amount) {
On 2015/02/02 21:00:54, Hannes Payer wrote:
Just create a filler here, that's easier. Moreover, we should make
sure that new
space is not growing. Just set the max_semi_space_size=1.
Thanks for the max_semi_space_size suggestion!
Unfortunately Heap::AllocateFillerObject() is a private method and I'm
not sure if we should change that, so I'll keep allocating arrays here.
https://codereview.chromium.org/880043003/
--
--
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.
