Temporary disable comparison of optimizability of code objects in some cases.

Temporary disable comparison of optimizability of code objects in some cases.

With crankshaft, a code object can change its optimizability: it can start as
optimizable code object, but later we can find out it was a bad idea to
optimize it.  Alas, currently we don't have a proper event to communicate
this back to logger.  Hence we temporary allow a code object to be viewed
as optimizable judging from logs while being unoptimizable judging from
heap traversal.

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

[antonm, 2011-01-31 19:00:43]

Misha,

small review for you.  If it's lgty, I'll file a bug.

[mnaganov (inactive), 2011-02-01 09:10:42]

LGTM.

I suppose, the transition between optimizable and unoptimizable code states is
unidirectional?

[antonm, 2011-02-01 12:38:38]

Thanks a lot for review, Mikhail.

On 2011/02/01 09:10:42, Mikhail Naganov (Chromium) wrote:
> LGTM.
> 
> I suppose, the transition between optimizable and unoptimizable code states is
> unidirectional?

As far as I know yes.