commit d3604cdb6808789e5f60b3f56f0ec2e992fad56c
author ssanfilippo <ssanfilippo@chromium.org> Wed Feb 10 11:26:14 2016
committer Commit bot <commit-bot@chromium.org> Wed Feb 10 11:26:34 2016
tree 335545e34307e1699271842108b0fcff365a92ee
parent 1d5a50d35d300c73ebe46fc2c8a893e7c3d2ec11

[Interpreter] Initial generate-bytecode-expectations implementation.

generate-bytecode-expectations is a tool intended to work together
with test/cctest/test-bytecode-generator.cc in order to produce a
meaningful diff between testcases and the actual bytecode being emitted.

It does so by parsing and compiling Javascript to bytecode,
constructing the same data structure in the testcase and then running a
textual diff between the expected (i.e. the one encoded in the unit test)
and actual (i.e. the one built from the compiler output) representation.

This commit is a first step in this direction, achieving just the first
half of what we desire. At the moment, bytecodechecker can:

* take a code snippet from the command line and emit the expected structure.
* adhere to the same formatting rules of the test cases
  (this one is important for text diff and for copy and pasting too)

Still to do:

* parse unit tests:
    + extract code snippets
    + indent the code to match the input test case
    + allow flexibility in the input format
    + try to recognize and work around some macro magic (i.e. REPEAT_127)
* emit the representation of the constant pool and handlers vector
* run a textual diff

BUG=v8:4280
LOG=N

Review URL: https://codereview.chromium.org/1671863002

Cr-Commit-Position: refs/heads/master@{#33863}