Hi, I am working on something experimental, it doesn't have to be 
productizable right away, but still wondering about a few memory related 
things, and was looking at how other aspects are handled in V8. If anybody 
reads this and could answer, would be greatly appreciated. I was wondering, 
What's the design decision for the SharedFunctionInfo to be a HeapObject 
and managed by V8's heap, instead of being part of the C/C++ memory? Since 
it is not really memory that is used by the Javascript program itself.
With respect to the optimized code map, when evicting one entry, we seem to 
call EvictFromOptimizedCodeMap and manipulate the map directly. But 
for ClearOptimizedCodeMap, we seem to use a CodeFlusher object that is 
somehow part of garbage collection in mark-compact.h, instead of 
manipulation the map directly. Why is that?

-- 
-- 
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.

Reply via email to