-
danno@chromium.org authored
During https://code.google.com/p/v8/source/detail?r=19925 checkin context bound scripts (Script) and context unbound scripts (UnboundScript) are Distinguished. And then Sven Panne helped to fix the vtune support compilation error in https://code.google.com/p/v8/source/detail?r=20955. The problem is that there is runtime error for vtune support. In our original implementation, we encapsulated and passed v8::internal::Script to V8 API. It will leads to type check error for current V8::Script definition. So I changed the Handle<Script> definition in JitCodeEvent to Handle<UnboundScript> and add the corresponding change in log.cc. If you do NOT prefer to change in include/v8.h. I think I can change the definition of CodeEventLogger::LogRecordedBuffer(...) so that the we can pass the correct type (JSFunction) as V8::Script to V8 API. BUG= R=danno@chromium.org, svenpanne@chromium.org Review URL: https://codereview.chromium.org/334263018 Patch from Chunyang Dai <chunyang.dai@intel.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22393 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
319e5226
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
ittnotify_config.h | ||
ittnotify_types.h | ||
jitprofiling.cc | ||
jitprofiling.h | ||
v8-vtune.h | ||
v8vtune.gyp | ||
vtune-jit.cc | ||
vtune-jit.h |