Changeset 220148 in webkit for trunk/Source/JavaScriptCore/jsc.cpp

Timestamp:

Aug 2, 2017, 12:57:50 PM (8 years ago)

Author:

[email protected]

Message:

We should be OK with the gigacage being disabled on gmalloc
​https://bugs.webkit.org/show_bug.cgi?id=175082

Reviewed by Michael Saboff.
Source/bmalloc:

This adds Gigacage::shouldBeEnabled(), which returns false when we're using gmalloc or other things
that enable DebugHeap.

• bmalloc/Environment.cpp:

(bmalloc::Environment::Environment):

• bmalloc/Environment.h:
• bmalloc/Gigacage.cpp:

(Gigacage::ensureGigacage):
(Gigacage::shouldBeEnabled):

• bmalloc/Gigacage.h:
• bmalloc/Heap.cpp:

(bmalloc::Heap::Heap):

• bmalloc/Heap.h:

Source/JavaScriptCore:

• jsc.cpp:

(jscmain):

Source/WebKit:

• WebProcess/WebProcess.cpp:

(WebKit::m_webSQLiteDatabaseTracker):

Source/WTF:

• wtf/Gigacage.h:

(Gigacage::shouldBeEnabled):

File:

• trunk/Source/JavaScriptCore/jsc.cpp (modified) (1 diff)

trunk/Source/JavaScriptCore/jsc.cpp

@@ -3827 +3827 @@
     JSC::Wasm::enableFastMemory();
 #endif
-    if (GIGACAGE_ENABLED)
+    if (Gigacage::shouldBeEnabled())
         Gigacage::addDisableCallback(gigacageDisabled, nullptr);