-
jochen@chromium.org authored
In R23940 (https://code.google.com/p/v8/source/detail?r=23940) it introduces Isolate::CreateParams and mentions that V8::SetJitCodeEventHandler should either be passed to Isolate::New as well, or invoked via the Isolate. When Chrome as embedder of V8, we will set the Jit Code event handler for Vtune support during the initialization of renderer process and V8 has be initialized at that time. It's better that we invoke V8::SetJitCodeEventHander via the Isolate. So we change the vTune::InitializeVtuneForV8(v8::Isolate::CreateParams& params) to vTune::InitializeVtuneForV8(v8::Isolate* isolate). we will do corresponding changes in chromium code if this patch is landed and Chromium updates V8 to the new release branch. some part of this patch is provided by denis.pravdin@intel.com. BUG= R=danno@chromium.org, jochen@chromium.org Review URL: https://codereview.chromium.org/655183002 Patch from Chunyang Dai <chunyang.dai@intel.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24811 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
7a70d6a0
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
fdlibm | ||
kernel/tools/perf/util | ||
valgrind | ||
vtune |