On 2012/05/11 12:58:35, Vyacheslav Egorov wrote:
> Hurry should also treat maps in a special way.
Done.
On 2012/05/11 12:58:35, Vyacheslav Egorov wrote:
> s/JS_MAP_TYPE/MAP_TYPE/
Already fixed in second patch set.
On 2012/05/11 12:58:35, Vyacheslav Egorov wrote:
> I suggest naming it MarkObjectAndPush
Done.
On 2012/05/11 12:58:35, Vyacheslav Egorov wrote:
> Can it be grey at this point? I don't think so.
Done, inlined mark bit setting.
On 2012/05/11 12:58:35, Vyacheslav Egorov wrote:
> long line
Done.
On 2012/05/11 12:58:35, Vyacheslav Egorov wrote:
> Usually we avoid to use function overloading (per style guide).
> In this case it's especially dangerous as MarkObject(HeapObject*) and
> MarkObject(HeapObject*, MarkBit) do _completely_ different things.
Done, renamed to MarkObjectAndPush().
On 2012/05/11 12:58:35, Vyacheslav Egorov wrote:
> It seems that running with --nocollect-maps would really cause maps
tree to be
> retained in both directions (from leaves to root and from root to
leaves).
Yes, now the flag treats pointers in both direction (i.e. "up the tree"
and "down the tree") as strong. But IMHO that is what the name of that
flag suggests.
You are right, we still need to figure out how to collect whole map
trees when their roots are unreachable. But that should be done without
a flag.
On 2012/05/11 12:58:35, Vyacheslav Egorov wrote:
> Why does not it depend on FLAG_collect_maps?
> Flag and this field have some very strange relation.
> Having something that is always true does not help.
> If you change it to false then potentially you might get broken heap
structure
> (back pointer from live map pointing to a dead map). So for now I
suggest we
> should either remove it or make it work.
Done, removed flag for now.
On 2012/05/11 12:58:35, Vyacheslav Egorov wrote:
> Try to move this to MarkMapContents to further share code?
Done.
On 2012/05/11 12:58:35, Vyacheslav Egorov wrote:
> empty line before definition
Done.
https://chromiumcodereview.appspot.com/10386046/