Risky plan, because what can you do with the object once you have got it
by
dereferencing the handle? It's being mutated by another thread that does
no
locking. You can test it for Smi-ness, but most other operations (look at
the
map, for example) are not safe.
Right. The GC isn't the only thing that mutates the HeapObject.
This is a problem because even if I manage gathering all the
information before I move the compilation to the second thread, how do
I know that the information is still valid when I compile (or _while_
I compile)? I think the right solution is to defer all those actions
to after the compilation has been done on the compiler thread. It
will be quite tricky to do that AND do a significant amount of work in
the compiler thread.
http://codereview.chromium.org/10640012/
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
