Use exact instruction names in the SSA tracer.

Use exact instruction names in the SSA tracer.

Before the mapping from HInstruction names to printed representations
used by the tracer was arbitrary.  Change it to use the HInstruction
name with a colon separating the arguments from the instruction name.
The first colon on the line is recognized by the tool as delimiting
the opcode.

Seeing the precise structure of the IR is more important than
having human-writable surface syntax.

BUG=
R=sra@google.com

Committed: https://github.com/dart-lang/sdk/commit/6efe664788663055edbaf32aacb62733472d1aaa

[Kevin Millikin (Google), 2016-03-21 10:27:23]

kmillikin@google.com changed reviewers:
+ sigmund@google.com, sra@google.com

[sra1, 2016-03-21 12:11:09]

lgtm

[Kevin Millikin (Google), 2016-03-21 12:25:30]

Description was changed from

==========
Use exact instruction names in the SSA tracer.

Before the mapping from HInstruction names to printed representations
used by the tracer was arbitrary.  Change it to use the HInstruction
name with a colon separating the arguments from the instruction name.
The first colon on the line is recognized by the tool as delimiting
the opcode.

Seeing the precise structure of the IR is more important than
having human-writable surface syntax.

BUG=
==========

to

==========
Use exact instruction names in the SSA tracer.

Before the mapping from HInstruction names to printed representations
used by the tracer was arbitrary.  Change it to use the HInstruction
name with a colon separating the arguments from the instruction name.
The first colon on the line is recognized by the tool as delimiting
the opcode.

Seeing the precise structure of the IR is more important than
having human-writable surface syntax.

BUG=
R=sra@google.com

Committed:
https://github.com/dart-lang/sdk/commit/6efe664788663055edbaf32aacb62733472d1aaa
==========

[Kevin Millikin (Google), 2016-03-21 12:25:32]

Committed patchset #1 (id:1) manually as
6efe664788663055edbaf32aacb62733472d1aaa (presubmit successful).