Reviewers: Søren Gjesse, Mads Ager,
Message:
Mads and Soeren,
Can you please take a look at the API for the C++ profiler? I think, it will
make sense to commit it together with wiring new profiles processor to VM,
so
API will be functional.
As for switching between old and new implementation, I suggest that I'll
introduce a preprocessor directive (because using a flag may have a
significant
performance penalty.) Or maybe it will make sense to initiate a parallel
branch,
as Erik previously did for new snapshots -- I'm not sure which approach is
better from production point of view.
Description:
[not for commit] V8 profiler API preview.
This API is enough for getting JS-only profiles (for DevTools.)
In order to replace tick processor scripts, it will be needed to
add the following:
- import of address -> function maps for C / C++ code;
- retrieval of processing statistics (unresolved ticks, etc.);
- filtering (for filtering ICs and by VM state);
- import and export of stubs / builtins names from snapshots;
Please review this at http://codereview.chromium.org/1105009
Affected files:
A include/v8-profiler.h
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
To unsubscribe from this group, send email to v8-dev+unsubscribegooglegroups.com or reply
to this email with the words "REMOVE ME" as the subject.
