Thread safety analysis: Eliminate parameter from intersectAndWarn (NFC)
authorAaron Puchert <aaron.puchert@sap.com>
Thu, 6 May 2021 21:07:40 +0000 (23:07 +0200)
committerAaron Puchert <aaron.puchert@sap.com>
Thu, 6 May 2021 21:07:42 +0000 (23:07 +0200)
commitd21e1b79ff7d40bca537c30da706e31e48483f21
tree77ce873bb51e7c3645223780afc0e3f2640bb706
parentfca10c8808ff22f3069359b2f6b2d410612c70c1
Thread safety analysis: Eliminate parameter from intersectAndWarn (NFC)

We were modifying precisely when intersecting the lock sets of multiple
predecessors without back edge. That's no coincidence: we can't modify
on back edges, it doesn't make sense to modify at the end of a function,
and otherwise we always want to intersect on forward edges, because we
can build a new lock set for those.

Reviewed By: aaron.ballman

Differential Revision: https://reviews.llvm.org/D101755
clang/lib/Analysis/ThreadSafety.cpp