Generalized the EvalCache into a CompilationCache and enabled...

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.

Committed: http://code.google.com/p/v8/source/detail?r=270

[Mads Ager (chromium), 2008-09-11 10:47:00]

LGTM

http://codereview.chromium.org/1933/diff/1/6
File src/compilation-cache.h (right):

http://codereview.chromium.org/1933/diff/1/6#newcode41
Line 41: // get the wrong kind of entry when looking up.
get -> getting