Print compare-state with --print-code-stubs.

Print compare-state with --print-code-stubs.

R=vegorov@chromium.org

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

[Vyacheslav Egorov (Chromium), 2012-04-26 15:39:51]

lgtm

https://chromiumcodereview.appspot.com/10235006/diff/1/src/code-stubs.cc
File src/code-stubs.cc (right):

https://chromiumcodereview.appspot.com/10235006/diff/1/src/code-stubs.cc#newc...
src/code-stubs.cc:121: RecordCodeGeneration(*new_object, &masm);
I think more logical would be to move code->set_major_key(MajorKey()); out of
RecordCodeGeneration to here and then move RecordCodeGeneration down after
FinishCode.

Recording generation of unfinished code looks strange.

[Michael Starzinger, 2012-04-26 16:19:58]

Added new patch set.

https://chromiumcodereview.appspot.com/10235006/diff/1/src/code-stubs.cc
File src/code-stubs.cc (right):

https://chromiumcodereview.appspot.com/10235006/diff/1/src/code-stubs.cc#newc...
src/code-stubs.cc:121: RecordCodeGeneration(*new_object, &masm);
On 2012/04/26 15:39:51, Vyacheslav Egorov wrote:
> I think more logical would be to move code->set_major_key(MajorKey()); out of
> RecordCodeGeneration to here and then move RecordCodeGeneration down after
> FinishCode.
> 
> Recording generation of unfinished code looks strange.

Done. But I still left the printing here. Because IMHO printing code has nothing
to do with recording code generation.