GC zapping logic could benefit from some more assertions
authorfpizlo@apple.com <fpizlo@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 6 Dec 2011 22:12:56 +0000 (22:12 +0000)
committerfpizlo@apple.com <fpizlo@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 6 Dec 2011 22:12:56 +0000 (22:12 +0000)
commit0739079c2a74a06615d236b2c31de787df21070b
tree74edd85c456a13c4f313710023b5290f416d1abf
parent383a04d2cdf6bd2e7970e10aab06e789e6beafd4
GC zapping logic could benefit from some more assertions
https://bugs.webkit.org/show_bug.cgi?id=73947

Reviewed by Gavin Barraclough.

- If you're in a zapped block and you're zapped, then your mark bit should
  never be set.

- If you're being marked, then you should never be zapped.

* heap/MarkedBlock.h:
(JSC::MarkedBlock::isLive):
* runtime/Structure.h:
(JSC::MarkStack::internalAppend):

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@102179 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Source/JavaScriptCore/ChangeLog
Source/JavaScriptCore/heap/MarkedBlock.h
Source/JavaScriptCore/runtime/Structure.h