[turbofan] Add a mutex for recording compilation statistics

[turbofan] Add a mutex for recording compilation statistics

There was previously a race between different phases recording their
first entry -- and thus, their insert order -- on the main and
concurrent-compilation thread. This would later manifest as a segfault
when creating the sorted array of phases for --turbo-stats (as two
phases would have the same insert order and so there would be a gap in
the array).

Committed: https://crrev.com/1df36a80de9d9d4a8967b976799fb9a7f5f384b3
Cr-Commit-Position: refs/heads/master@{#41669}

[Leszek Swirski, 2016-12-13 11:08:59]

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

[commit-bot: I haz the power, 2016-12-13 11:09:08]

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

[Leszek Swirski, 2016-12-13 11:23:50]

Description was changed from

==========
[turbofan] Add a mutex for recording complicaitons statistics

There was previously a race between different phases recording their
first entry -- and thus, their insert order -- on the main and
concurrent-compliation thread. This would later manifest as a segfault
when creating the sorted array of phases for --turbo-stats (as two
phases would have the same insert order and so there would be a gap in
the array).
==========

to

==========
[turbofan] Add a mutex for recording compilation statistics

There was previously a race between different phases recording their
first entry -- and thus, their insert order -- on the main and
concurrent-compilation thread. This would later manifest as a segfault
when creating the sorted array of phases for --turbo-stats (as two
phases would have the same insert order and so there would be a gap in
the array).
==========

[Leszek Swirski, 2016-12-13 11:24:43]

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

[Leszek Swirski, 2016-12-13 11:24:43]

Hi Benedikt,

I came across this issue while profiling, could you take a look?

[commit-bot: I haz the power, 2016-12-13 11:33:44]

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

[commit-bot: I haz the power, 2016-12-13 11:33:45]

Dry run: This issue passed the CQ dry run.

[Benedikt Meurer, 2016-12-13 12:10:09]

Nice, thanks. LGTM.

[Leszek Swirski, 2016-12-13 12:12:25]

The CQ bit was checked by leszeks@chromium.org

[commit-bot: I haz the power, 2016-12-13 12:12:29]

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-12-13 12:14:05]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1481631145777030, "parent_rev":
"eb597f1b58e6fc50d37768eab8d5ca011b57f853", "commit_rev":
"a6084799a118cb7ec060fc57dcdadc86642f8d8b"}

[commit-bot: I haz the power, 2016-12-13 12:14:12]

Description was changed from

==========
[turbofan] Add a mutex for recording compilation statistics

There was previously a race between different phases recording their
first entry -- and thus, their insert order -- on the main and
concurrent-compilation thread. This would later manifest as a segfault
when creating the sorted array of phases for --turbo-stats (as two
phases would have the same insert order and so there would be a gap in
the array).
==========

to

==========
[turbofan] Add a mutex for recording compilation statistics

There was previously a race between different phases recording their
first entry -- and thus, their insert order -- on the main and
concurrent-compilation thread. This would later manifest as a segfault
when creating the sorted array of phases for --turbo-stats (as two
phases would have the same insert order and so there would be a gap in
the array).

Review-Url: https://codereview.chromium.org/2572713003
==========

[commit-bot: I haz the power, 2016-12-13 12:14:12]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-13 12:15:24]

Description was changed from

==========
[turbofan] Add a mutex for recording compilation statistics

There was previously a race between different phases recording their
first entry -- and thus, their insert order -- on the main and
concurrent-compilation thread. This would later manifest as a segfault
when creating the sorted array of phases for --turbo-stats (as two
phases would have the same insert order and so there would be a gap in
the array).

Review-Url: https://codereview.chromium.org/2572713003
==========

to

==========
[turbofan] Add a mutex for recording compilation statistics

There was previously a race between different phases recording their
first entry -- and thus, their insert order -- on the main and
concurrent-compilation thread. This would later manifest as a segfault
when creating the sorted array of phases for --turbo-stats (as two
phases would have the same insert order and so there would be a gap in
the array).

Committed: https://crrev.com/1df36a80de9d9d4a8967b976799fb9a7f5f384b3
Cr-Commit-Position: refs/heads/master@{#41669}
==========

[commit-bot: I haz the power, 2016-12-13 12:15:24]

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