tree 77ce873bb51e7c3645223780afc0e3f2640bb706
parent fca10c8808ff22f3069359b2f6b2d410612c70c1
author Aaron Puchert <aaron.puchert@sap.com> 1620335260 +0200
committer Aaron Puchert <aaron.puchert@sap.com> 1620335262 +0200

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