[deoptimizer] Use TranslationIterator for OptimizedFrame again.

[deoptimizer] Use TranslationIterator for OptimizedFrame again.

Using TranslatedState and friends is too expensive compared to the low
level TranslationIterator, because some code (i.e. in Speedometer)
depends on the OptimizedFrame summary/function listing to be very fast.

BUG=chromium:499338
LOG=n
R=jarin@chromium.org

Committed: https://crrev.com/2c44f4f9deb4015555b7825c81861b06c33f346d
Cr-Commit-Position: refs/heads/master@{#29037}

[Benedikt Meurer, 2015-06-16 05:33:07]

Hey Jaro,

This is the "performance fix" for speedometer. Basically reverts the previoius
change to use TranslatedState and friends, with some refactoring. Please take a
look.

Thanks,
Benedikt

[Jarin, 2015-06-16 05:36:03]

lgtm. 

However, it would be nice to know whether it was GetFunctions or Summarize that
tanked the benchmarks - my feeling is that Summarize could (and should) still
use the TranslatedState utility.

[Benedikt Meurer, 2015-06-16 05:39:23]

> However, it would be nice to know whether it was GetFunctions or Summarize
that
> tanked the benchmarks - my feeling is that Summarize could (and should) still
> use the TranslatedState utility.

Speedometer is too flaky to tell for sure. But it seems like we need both,
because Summarize is used to capture current stack trace.

[Benedikt Meurer, 2015-06-16 05:39:26]

The CQ bit was checked by bmeurer@chromium.org

[commit-bot: I haz the power, 2015-06-16 05:39:36]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1181373003/1

[commit-bot: I haz the power, 2015-06-16 06:04:47]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-06-16 06:05:01]

Patchset 1 (id:??) landed as
https://crrev.com/2c44f4f9deb4015555b7825c81861b06c33f346d
Cr-Commit-Position: refs/heads/master@{#29037}