Do not create a SharedFunctionInfo for closures on each recompilation.

Do not create a SharedFunctionInfo for closures on each recompilation.

Unoptimized code should already keep a reference to the SharedFunctionInfo,
let's use it instead of allocating a new object and prohibiting SharedFunctionInfo
specific optimizations.

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

[antonm, 2011-04-01 09:37:41]

Guys,

may you have a look?

Search algorithm is quite simple.  If it'll prove to be a problem we can easily
improve it emitting a separate list of emitted SFIs.

[Kevin Millikin (Chromium), 2011-04-01 10:15:06]

LGTM.

We could also consider the same trick when we are recompiling the unoptimized
code to attach deoptimization info.

Maybe we could do something simple like inspect the CompilationInfo's
SharedFunctionInfo to see if it has code that's not the lazy compilation stub.