Remove SafePointAwareMutexLocker

Remove SafePointAwareMutexLocker

Now that we have the per-thread heaps, we no longer need SafePointAwareMutexLocker
(because a GCing thread doesn't need to stop other threads that may be waiting on the locker).
We can just use MutexLocker.

BUG=671856
Review-Url: https://codereview.chromium.org/2691073004
Cr-Commit-Position: refs/heads/master@{#450314}
Committed: https://chromium.googlesource.com/chromium/src/+/80d8d295c8f2445ef62ceff89668b15b15ae644d

[haraken, 2017-02-14 08:23:17]

haraken@chromium.org changed reviewers:
+ sigbjornf@opera.com

[haraken, 2017-02-14 08:23:18]

PTAL

[sof, 2017-02-14 08:31:38]

https://codereview.chromium.org/2691073004/diff/1/third_party/WebKit/Source/p...
File third_party/WebKit/Source/platform/heap/Heap.cpp (right):

https://codereview.chromium.org/2691073004/diff/1/third_party/WebKit/Source/p...
third_party/WebKit/Source/platform/heap/Heap.cpp:579: void
ThreadHeap::leaveSafePoint() {
we can just remove this altogether.

[haraken, 2017-02-14 08:50:49]

https://codereview.chromium.org/2691073004/diff/1/third_party/WebKit/Source/p...
File third_party/WebKit/Source/platform/heap/Heap.cpp (right):

https://codereview.chromium.org/2691073004/diff/1/third_party/WebKit/Source/p...
third_party/WebKit/Source/platform/heap/Heap.cpp:579: void
ThreadHeap::leaveSafePoint() {
On 2017/02/14 08:31:38, sof wrote:
> we can just remove this altogether.

Yeah, I want to do that in a follow-up where I'll move pushAllRegisters out of
SafePoint.cpp, which enables to remove enterSafePoint and leaveSafePoint at the
same time.

[sof, 2017-02-14 08:52:09]

On 2017/02/14 08:50:49, haraken wrote:
>
https://codereview.chromium.org/2691073004/diff/1/third_party/WebKit/Source/p...
> File third_party/WebKit/Source/platform/heap/Heap.cpp (right):
> 
>
https://codereview.chromium.org/2691073004/diff/1/third_party/WebKit/Source/p...
> third_party/WebKit/Source/platform/heap/Heap.cpp:579: void
> ThreadHeap::leaveSafePoint() {
> On 2017/02/14 08:31:38, sof wrote:
> > we can just remove this altogether.
> 
> Yeah, I want to do that in a follow-up where I'll move pushAllRegisters out of
> SafePoint.cpp, which enables to remove enterSafePoint and leaveSafePoint at
the
> same time.

sounds good, lgtm.

[haraken, 2017-02-14 08:52:44]

The CQ bit was checked by haraken@chromium.org

[commit-bot: I haz the power, 2017-02-14 08:53:09]

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-02-14 10:30:56]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1487062364184460, "parent_rev":
"4ce9a407ae2f2299f9d62016fd5a4c71e3dc49d5", "commit_rev":
"80d8d295c8f2445ef62ceff89668b15b15ae644d"}

[commit-bot: I haz the power, 2017-02-14 10:31:32]

Description was changed from

==========
Remove SafePointAwareMutexLocker

Now that we have the per-thread heaps, we no longer need
SafePointAwareMutexLocker
(because a GCing thread doesn't need to stop other threads that may be waiting
on the locker).
We can just use MutexLocker.

BUG=671856
==========

to

==========
Remove SafePointAwareMutexLocker

Now that we have the per-thread heaps, we no longer need
SafePointAwareMutexLocker
(because a GCing thread doesn't need to stop other threads that may be waiting
on the locker).
We can just use MutexLocker.

BUG=671856

Review-Url: https://codereview.chromium.org/2691073004
Cr-Commit-Position: refs/heads/master@{#450314}
Committed:
https://chromium.googlesource.com/chromium/src/+/80d8d295c8f2445ef62ceff89668...
==========

[commit-bot: I haz the power, 2017-02-14 10:31:33]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/80d8d295c8f2445ef62ceff89668...