<rdar://problem/5951561> Turn on JavaScript Profiler
authoroliver@apple.com <oliver@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Fri, 23 May 2008 08:56:21 +0000 (08:56 +0000)
committeroliver@apple.com <oliver@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Fri, 23 May 2008 08:56:21 +0000 (08:56 +0000)
commitddb4622ee3fc29770db64a9f258374da95cf5f2f
treec7fb91074ddf4cfca82c9071d380bf92af668d9a
parent93d24c17853d68dfbccea6c0598a764b2b89ca7b
<rdar://problem/5951561> Turn on JavaScript Profiler

Reviewed by Kevin McCullough

Flipped the switch on the profiler, rearranged how we
signal the the profiler is active so that calls aren't
needed in the general case.

Also fixed the entry point for Machine::execute(FunctionBodyNode..)
to correctly indicate function exit.

Results in a 0.7-1.0% regression in SunSpider :-(

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@34065 268f45cc-cd09-0410-ab3c-d52691b4dbfc
JavaScriptCore/ChangeLog
JavaScriptCore/VM/Machine.cpp
JavaScriptCore/kjs/config.h
JavaScriptCore/profiler/Profiler.cpp
JavaScriptCore/profiler/Profiler.h