Ignore:
Timestamp:
Nov 16, 2008, 2:05:23 AM (17 years ago)
Author:
[email protected]
Message:

Reviewed by Dan Bernstein.

https://bugs.webkit.org/show_bug.cgi?id=22290
Remove cross-heap GC and MessagePort multi-threading support

It is broken (and may not be implementable at all), and no longer needed, as we
don't use MessagePorts for communication with workers any more.

JavaScriptCore:

  • JavaScriptCore.exp:
  • runtime/Collector.cpp: (JSC::Heap::collect):
  • runtime/JSGlobalObject.cpp:
  • runtime/JSGlobalObject.h: Remove hooks for cross-heap GC.

WebCore:

  • bindings/js/JSDOMBinding.cpp:
  • bindings/js/JSDOMBinding.h:
  • bindings/js/JSDOMWindowBase.cpp:
  • bindings/js/JSDOMWindowBase.h: Removed cross-heap GC implementation.
  • dom/MessagePort.cpp: (WebCore::MessagePort::hasPendingActivity):
  • dom/MessagePort.h: Made objects RefCounted instead of ThreadSafeShared, added FIXME comments for code that is unnecessarily complicated for single threaded case.
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/JavaScriptCore/runtime/Collector.cpp

    r38423 r38444  
    985985    m_globalData->smallStrings.mark();
    986986
    987     JSGlobalObject* globalObject = m_globalData->head;
    988     if (globalObject) {
    989         do {
    990             globalObject->markCrossHeapDependentObjects();
    991             globalObject = globalObject->next();
    992         } while (globalObject != m_globalData->head);
    993     }
    994 
    995987    JAVASCRIPTCORE_GC_MARKED();
    996988
Note: See TracChangeset for help on using the changeset viewer.