Interpreter tester should accept metadata instead of a vector

Interpreter tester should accept metadata instead of a vector

The InterpreterTester class cobbles together a JSFunction from
a manually created bytecode and feedback vector. However it's
fragile against design changes in the way literal arrays and
feedback vectors are handled. It's better to let it hand in
a feedback vector metadata object, and allow the system to
create the vector from that.

BUG=v8:5456
Review-Url: https://codereview.chromium.org/2652893010
Cr-Commit-Position: refs/heads/master@{#42684}
Committed: https://chromium.googlesource.com/v8/v8/+/d24ce605c99f5b45e596e88931127d6ce6d0d27a

[mvstanton, 2017-01-26 09:29:57]

mvstanton@chromium.org changed reviewers:
+ rmcilroy@chromium.org

[mvstanton, 2017-01-26 09:29:58]

Hi Ross,
Here is the CL I mentioned, thanks!
--Michael

[mvstanton, 2017-01-26 09:30:05]

The CQ bit was checked by mvstanton@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-01-26 09:30:13]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[rmcilroy, 2017-01-26 09:34:15]

LGTM, thanks

[rmcilroy, 2017-01-26 09:34:16]

LGTM, thanks

[mvstanton, 2017-01-26 09:36:06]

The CQ bit was checked by mvstanton@chromium.org

[commit-bot: I haz the power, 2017-01-26 09:36:12]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-26 10:03:01]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1485423366052240, "parent_rev":
"a5e7382d846c620ceb62fdf02e8ee24794aa7775", "commit_rev":
"d24ce605c99f5b45e596e88931127d6ce6d0d27a"}

[commit-bot: I haz the power, 2017-01-26 10:03:05]

Description was changed from

==========
Interpreter tester should accept metadata instead of a vector

The InterpreterTester class cobbles together a JSFunction from
a manually created bytecode and feedback vector. However it's
fragile against design changes in the way literal arrays and
feedback vectors are handled. It's better to let it hand in
a feedback vector metadata object, and allow the system to
create the vector from that.

BUG=v8:5456
==========

to

==========
Interpreter tester should accept metadata instead of a vector

The InterpreterTester class cobbles together a JSFunction from
a manually created bytecode and feedback vector. However it's
fragile against design changes in the way literal arrays and
feedback vectors are handled. It's better to let it hand in
a feedback vector metadata object, and allow the system to
create the vector from that.

BUG=v8:5456

Review-Url: https://codereview.chromium.org/2652893010
Cr-Commit-Position: refs/heads/master@{#42684}
Committed:
https://chromium.googlesource.com/v8/v8/+/d24ce605c99f5b45e596e88931127d6ce6d...
==========

[commit-bot: I haz the power, 2017-01-26 10:03:06]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/v8/v8/+/d24ce605c99f5b45e596e88931127d6ce6d...