Remove ThreadState::m_isAtSafePoint

Remove ThreadState::m_isAtSafePoint

It's safe to remove an !isAtSafePoint() check from isAllocationAllowed()
because ThreadState::collectGarbage already enters NoAllocationScope
before running a GC.

BUG=671856
Review-Url: https://codereview.chromium.org/2694243003
Cr-Commit-Position: refs/heads/master@{#450656}
Committed: https://chromium.googlesource.com/chromium/src/+/2a697ce8b8f7be1dbd33c335648b7ce83b1bc71e

[haraken, 2017-02-15 08:50:10]

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

[haraken, 2017-02-15 08:50:11]

PTAL

[sof, 2017-02-15 09:00:04]

lgtm

https://codereview.chromium.org/2694243003/diff/1/third_party/WebKit/Source/p...
File third_party/WebKit/Source/platform/heap/ThreadState.cpp (left):

https://codereview.chromium.org/2694243003/diff/1/third_party/WebKit/Source/p...
third_party/WebKit/Source/platform/heap/ThreadState.cpp:1155:
m_heap->leaveSafePoint();
dead code.

[haraken, 2017-02-15 09:02:29]

https://codereview.chromium.org/2694243003/diff/1/third_party/WebKit/Source/p...
File third_party/WebKit/Source/platform/heap/ThreadState.cpp (left):

https://codereview.chromium.org/2694243003/diff/1/third_party/WebKit/Source/p...
third_party/WebKit/Source/platform/heap/ThreadState.cpp:1155:
m_heap->leaveSafePoint();
On 2017/02/15 09:00:04, sof wrote:
> dead code.

yeah, let me remove this when I remove SafePointScope.

[haraken, 2017-02-15 09:02:33]

The CQ bit was checked by haraken@chromium.org

[commit-bot: I haz the power, 2017-02-15 09:02:52]

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-15 10:42:25]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1487149353399080, "parent_rev":
"c3c9701cc44e6cb38e78c8e1d9d2bca5a74726a4", "commit_rev":
"2a697ce8b8f7be1dbd33c335648b7ce83b1bc71e"}

[commit-bot: I haz the power, 2017-02-15 10:43:01]

Description was changed from

==========
Remove ThreadState::m_isAtSafePoint

It's safe to remove an !isAtSafePoint() check from isAllocationAllowed()
because ThreadState::collectGarbage already enters NoAllocationScope
before running a GC.

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

to

==========
Remove ThreadState::m_isAtSafePoint

It's safe to remove an !isAtSafePoint() check from isAllocationAllowed()
because ThreadState::collectGarbage already enters NoAllocationScope
before running a GC.

BUG=671856

Review-Url: https://codereview.chromium.org/2694243003
Cr-Commit-Position: refs/heads/master@{#450656}
Committed:
https://chromium.googlesource.com/chromium/src/+/2a697ce8b8f7be1dbd33c335648b...
==========

[commit-bot: I haz the power, 2017-02-15 10:43:02]

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