Ignore:
Timestamp:
May 25, 2021, 5:37:19 PM (4 years ago)
Author:
Chris Dumez
Message:

Use UncheckedLock less in JavaScriptCore
https://bugs.webkit.org/show_bug.cgi?id=226212

Reviewed by Saam Barati.

Source/JavaScriptCore:

Use UncheckedLock less in JavaScriptCore as it is being phased out in favor of Lock, which
enables Clang thread safety analysis.

  • assembler/testmasm.cpp:
  • dfg/DFGCommon.cpp:
  • dynbench.cpp:
  • heap/Heap.cpp:
  • heap/Heap.h:
  • inspector/remote/socket/RemoteInspectorSocketEndpoint.h:
  • runtime/JSLock.cpp:
  • runtime/JSLock.h:
  • runtime/VM.h:

Source/WTF:

Add support for unlockEarly() to Locker<Lock> specialization, for consistency
with the generic Locker.

  • wtf/Lock.h:
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/JavaScriptCore/dfg/DFGCommon.cpp

    r277943 r278069  
    3636const char* const tierName = "DFG ";
    3737
    38 static UncheckedLock crashLock;
     38static Lock crashLock;
    3939
    40 void startCrashing()
     40// Use WTF_IGNORES_THREAD_SAFETY_ANALYSIS since the function keeps holding the lock when returning.
     41void startCrashing() WTF_IGNORES_THREAD_SAFETY_ANALYSIS
    4142{
    4243    crashLock.lock();
Note: See TracChangeset for help on using the changeset viewer.