[all-commits] [llvm/llvm-project] 2d7f53: Thread Safety Analysis: Use replaceLock instead of...

[Marco Elver via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 2d7f53bc27c345b844013b0a64040119bd362e51
      https://github.com/llvm/llvm-project/commit/2d7f53bc27c345b844013b0a64040119bd362e51
  Author: Marco Elver <elver at google.com>
  Date:   2025-06-05 (Thu, 05 Jun 2025)

  Changed paths:
    M clang/lib/Analysis/ThreadSafety.cpp

  Log Message:
  -----------
  Thread Safety Analysis: Use replaceLock instead of removeLock+addLock (#141500)

In ScopedLockableFactEntry::unlock(), we can avoid a second search,
pop_back(), and push_back() if we use the already obtained iterator into
the FactSet to replace the old FactEntry and take its position in the
vector.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications