Disable the compilation caching for scripts to make it
authorkasperl@chromium.org <kasperl@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 3 Mar 2009 13:35:05 +0000 (13:35 +0000)
committerkasperl@chromium.org <kasperl@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 3 Mar 2009 13:35:05 +0000 (13:35 +0000)
commit9f787147179a1ae0efd808487cb5f9749175c328
tree0051183a2c76b880b177829cef37b3ced9c8cd73
parent92aa4ab36ca9db4fed339e1b40cd2f46ba71c12f
Disable the compilation caching for scripts to make it
possible to start generating code specific to a global
object. We should start caching scripts but make the
mechanism local to a specific global context inspired
by the way we handle eval-caching.
Review URL: http://codereview.chromium.org/40007

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1406 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/codegen-ia32.cc
src/compilation-cache.cc
src/compilation-cache.h
src/compiler.cc
src/macro-assembler-ia32.cc