kasperl@chromium.org b5a72a1645 Generalized the EvalCache into a CompilationCache and enabled ... it for scripts too. In the context of Chromium, this should have a very positive impact on memory consumption for web apps that run multiple tabs from the same domain with a lot of the same JavaScript code. For now, the cache retirement policy is really simple: Whenever a mark-sweep collection is started we clear the cache. This guarantees that this change will not have a huge negative impact on memory consumption, but it may not be ideal. We should consider a more sophisticated LRU scheme. Review URL: http://codereview.chromium.org/1933 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@270 ce2b1a6d-e550-0410-aec6-3dcde31c8c00		2008-09-11 10:51:52 +00:00
benchmarks	Changed copyright header from google inc. to v8 project authors.	2008-09-09 20:08:45 +00:00
include	Removed Message::GetStackTrace.	2008-09-11 07:29:25 +00:00
samples	Removed Message::GetStackTrace.	2008-09-11 07:29:25 +00:00
src	Generalized the EvalCache into a CompilationCache and enabled	2008-09-11 10:51:52 +00:00
test	Generalized the EvalCache into a CompilationCache and enabled	2008-09-11 10:51:52 +00:00
tools	Generalized the EvalCache into a CompilationCache and enabled	2008-09-11 10:51:52 +00:00
AUTHORS	Capitalize V8 in AUTHORS file.	2008-09-08 08:09:50 +00:00
ChangeLog	Update version string and ChangeLog, we are now working on version	2008-09-11 08:42:29 +00:00
codereview.settings	Add support for setting the correct parameters for gcl and	2008-09-09 03:27:06 +00:00
LICENSE	Initial export.	2008-07-03 15:10:15 +00:00
SConstruct	Changed copyright header from google inc. to v8 project authors.	2008-09-09 20:08:45 +00:00