Ignore:
Timestamp:
Apr 5, 2017, 12:58:02 AM (8 years ago)
Author:
Carlos Garcia Campos
Message:

Implement PromiseDeferredTimer for non CF based ports
https://bugs.webkit.org/show_bug.cgi?id=170391

Reviewed by Yusuke Suzuki.

RunLoop handling is only implemented for CF causing several wasm tests to fail for other ports.

  • jsc.cpp:

(runJSC): Remove CF ifdefs.

  • runtime/PromiseDeferredTimer.cpp:

(JSC::PromiseDeferredTimer::doWork): Add non CF implementation using WTF RunLoop.
(JSC::PromiseDeferredTimer::runRunLoop): Ditto.

  • runtime/PromiseDeferredTimer.h:
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/JavaScriptCore/runtime/PromiseDeferredTimer.h

    r214504 r214936  
    6262
    6363    void stopRunningTasks() { m_runTasks = false; }
    64 #if USE(CF)
     64
    6565    JS_EXPORT_PRIVATE void runRunLoop();
    66 #endif
    6766
    6867private:
     
    7069    Lock m_taskLock;
    7170    bool m_runTasks { true };
    72 #if USE(CF)
    7371    bool m_shouldStopRunLoopWhenAllPromisesFinish { false };
    74 #endif
    7572    Vector<std::tuple<JSPromiseDeferred*, Task>> m_tasks;
    7673    HashMap<JSPromiseDeferred*, Vector<Task>> m_blockedTasks;
Note: See TracChangeset for help on using the changeset viewer.