I agree with Sven here. We've been working very hard at making the JS/C++
transitions really fast, I think setting the VM state in these cases is not
a
good idea.
It was exactly due to performance concerns that we don't set VM state when
CallApiFunctionAndReturn is used elsewhere. Adding this overhead for all
native
getters and setters just to support the very rare case when the sampling
profiler is active is the wrong tradeoff.
https://codereview.chromium.org/16286016/
--
--
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.
