On 2013/11/11 12:38:50, yurys wrote:
I assume that this won't trigger GC on each allocation when allocation
tracking
is enabled and that the object will be allocated in the same space as it
would
have been with inline allocation. We could address the latter in the
runtime
by
replicating inline logic there when tracking is on but we shouldn't cause
extra
GCs.
Yes, this will only trigger a GC if bump-pointer allocation as well as
free-list
allocation both fail and the space is not being expanded. Since the
bump-pointer
allocation in the runtime is semantically the same as the inlined version in
MacroAssembler::Allocate, I don't see a particular reason why the allocation
would turn out to land on a different page. In short: this should not
introduce
extra GCs AFAICT.
I agree that the label "gc_required" is named misleadingly in that regard.
https://codereview.chromium.org/65043006/
--
--
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.
