Remove the compiled_transitions flag and cleanup the unused code.

The compiled_transitions flag was enabled for quite some time now and seems to work out quite well, so time has come to remove the obsolete code paths and remove the unused methods.

R=mvstanton@chromium.org

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

[mvstanton, 2013-07-11 13:11:20]

I think I'd turn on the flag first, verify that chrome stability is good and
performance is good as well, then remove the flag after a week. Too
conservative? :)
--Michael

[Benedikt Meurer, 2013-07-11 13:33:25]

On 2013/07/11 13:11:20, mvstanton wrote:
> I think I'd turn on the flag first, verify that chrome stability is good and
> performance is good as well, then remove the flag after a week. Too
> conservative? :)
> --Michael

See https://codereview.chromium.org/19005005

[danno, 2013-07-11 13:56:35]

Yes, experience has shown that you should leave all the old code in for the
short term. Also, don't enable in this CL. Just put in all the new
functionality. Then, add another separate CL that just enabled the flag so that
a simple rollback can disable again if something goes wrong.

[Benedikt Meurer, 2013-07-11 13:57:34]

On 2013/07/11 13:56:35, danno wrote:
> Yes, experience has shown that you should leave all the old code in for the
> short term. Also, don't enable in this CL. Just put in all the new
> functionality. Then, add another separate CL that just enabled the flag so
that
> a simple rollback can disable again if something goes wrong.

Yep, done in https://codereview.chromium.org/19005005

[Benedikt Meurer, 2013-07-29 07:35:46]

REBASE

[Benedikt Meurer, 2013-07-29 07:38:29]

compiled_transitions was enabled by default for some time now.

PTAL

[mvstanton, 2013-07-29 07:56:08]

This is neat. lgtm. :)

[Benedikt Meurer, 2013-07-29 09:12:30]

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