Fix up internalized strings after deserializing user code.

Fix up internalized strings after deserializing user code.

R=mvstanton@chromium.org

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

[mvstanton, 2014-07-14 13:31:03]

Hi Yang,
LGTM.

Just one comment regarding a safeguard for the feature on the association
between source string and cache data.
--Michael

https://codereview.chromium.org/387343002/diff/20001/test/cctest/test-seriali...
File test/cctest/test-serialize.cc (right):

https://codereview.chromium.org/387343002/diff/20001/test/cctest/test-seriali...
test/cctest/test-serialize.cc:724: TEST(SerializeToplevelInternalizedString) {
Per our discussion, it might be nice in debug mode to try and prevent a mismatch
between a script and cache data for that script. It makes sense to say it's up
to the embedder to avoid that, but maybe we can do something in debug mode. We
talked about the source string (slated to be removed), about the notion of a CRC
on the source string (too expensive, at least in release), and about the notion
of a version.

[Yang, 2014-07-15 08:46:56]

Committed patchset #2 manually as r22398 (presubmit successful).