Use optimized code map to cache OSR code.

src/code-stubs-hydrogen.cc

Index: src/code-stubs-hydrogen.cc
diff --git a/src/code-stubs-hydrogen.cc b/src/code-stubs-hydrogen.cc
index e52ec65c4b7632ac81cb082bfcd5d727cce3a574..b04403ff80778ee0e70ddff4aa76e40efdc5467c 100644
--- a/src/code-stubs-hydrogen.cc
+++ b/src/code-stubs-hydrogen.cc
@@ -1189,6 +1189,10 @@ void CodeStubGraphBuilderBase::BuildInstallFromOptimizedCodeMap(
     // optimized_map points to fixed array of 3-element entries
     // (native context, optimized code, literals).
     // Map must never be empty, so check the first elements.
+    // Matching code that we find may have been compiled for OSR as opposed to
+    // regular optimized code.  That is probably because we never had the
+    // chance to compile regular optimized code before OSR engaged.  In that
+    // case, it's probably a good idea to just reuse that OSR code right now.

[Michael Starzinger, 2013/12/03 15:27:32]

I strongly disagree that this is a good idea! Once Ben's work is done, it will
be incorrect to do that. This will just take whatever code is in the
optimized_map and smash it into the JSFunction. OSR code should not be installed
into JSFunctions at all.

     Label install_optimized;
     HValue* first_context_slot = Add<HLoadNamedField>(optimized_map,
         HObjectAccess::ForFirstContextSlot());