Custom objdump to enable perf annotation

Custom objdump to enable perf annotation

Allows jitted code to be annotated in perf. To use:

1) Report generated code in code-(pid)-1.asm.

  perf record -- d8 --print-code --redirect-code-traces script.js

2) Run perf report from the directory containing the above code file.

  perf report --objdump=v8/tools/objdump-v8

This script supports generated code from both crankshaft or turbofan.

BUG=

Committed: https://crrev.com/dbba4b40be3beeaf4834c971d88dd94bf43db8f5
Cr-Commit-Position: refs/heads/master@{#37913}

[mattloring, 2016-07-20 00:10:05]

mattloring@google.com changed reviewers:
+ jarin@chromium.org, ofrobots@google.com

[Jarin, 2016-07-20 08:46:08]

lgtm

[mattloring, 2016-07-20 14:41:55]

The CQ bit was checked by mattloring@google.com to run a CQ dry run

[commit-bot: I haz the power, 2016-07-20 14:42:04]

Dry run: 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, 2016-07-20 15:02:51]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-07-20 15:02:52]

Dry run: This issue passed the CQ dry run.

[mattloring, 2016-07-20 16:55:52]

The CQ bit was checked by mattloring@google.com

[commit-bot: I haz the power, 2016-07-20 16:56:02]

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, 2016-07-20 16:58:44]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-20 16:58:45]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-07-20 16:59:36]

Description was changed from

==========
Custom objdump to enable perf annotation

Allows jitted code to be annotated in perf. To use:

1) Report generated code in code-(pid)-1.asm.

  perf record -- d8 --print-code --redirect-code-traces script.js

2) Run perf report from the directory containing the above code file.

  perf report --objdump=v8/tools/objdump-v8

This script supports generated code from both crankshaft or turbofan.

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

to

==========
Custom objdump to enable perf annotation

Allows jitted code to be annotated in perf. To use:

1) Report generated code in code-(pid)-1.asm.

  perf record -- d8 --print-code --redirect-code-traces script.js

2) Run perf report from the directory containing the above code file.

  perf report --objdump=v8/tools/objdump-v8

This script supports generated code from both crankshaft or turbofan.

BUG=

Committed: https://crrev.com/dbba4b40be3beeaf4834c971d88dd94bf43db8f5
Cr-Commit-Position: refs/heads/master@{#37913}
==========

[commit-bot: I haz the power, 2016-07-20 16:59:37]

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

[Benedikt Meurer, 2016-07-21 03:50:34]

bmeurer@chromium.org changed reviewers:
+ bmeurer@chromium.org

[Benedikt Meurer, 2016-07-21 03:50:34]

https://codereview.chromium.org/2167553002/diff/1/tools/objdump-v8
File tools/objdump-v8 (right):

https://codereview.chromium.org/2167553002/diff/1/tools/objdump-v8#newcode60
tools/objdump-v8:60: codefile = "code-" + match.group(1) + "-1.asm"
d8 hardcodes code.asm as output, so this will not work for d8 itself. Can you
just fallback to code.asm if the code-<pid>-<isolate>.asm file is not found?