Fix concurrent osr.

Fix concurrent osr.

InstallOptimizedCode aquires ownership on the compilation info and deletes
it on return, tearing down the attached zone.  The OptimizingCompiler
object is a zone object allocated in just that zone, so it also gets
deleted.  Effectively, InstallOptimizedCode cleans up when it's done, so
the OptimizingCompiler object it receives is invalidated afterwards.

R=titzer@chromium.org
BUG=

Committed: https://code.google.com/p/v8/source/detail?r=16609

[Yang, 2013-09-10 09:21:30]

On 2013/09/10 09:20:29, Yang wrote:

We could also solve this by not having InstallOptimizedCode delete the
OptimizingCompiler object, but delete it manually later on.

[titzer, 2013-09-10 11:02:42]

lgtm

https://codereview.chromium.org/23769007/diff/1/src/compiler.cc
File src/compiler.cc (right):

https://codereview.chromium.org/23769007/diff/1/src/compiler.cc#newcode1227
src/compiler.cc:1227: BailoutId ast_id = compiler->info()->osr_ast_id();
I'm not sure why you pulled this variable out of its scope to this point.

[Yang, 2013-09-10 11:09:31]

Committed patchset #1 manually as r16609 (presubmit successful).