diff options
| author | Vedant Kumar <vsk@apple.com> | 2020-11-05 16:41:31 -0800 |
|---|---|---|
| committer | Vedant Kumar <vsk@apple.com> | 2020-11-05 16:56:37 -0800 |
| commit | 65d15fefe3392b1db2f679b3df029d43d8d26d2d (patch) | |
| tree | 62d71fd9e027c02f4a5eb4cd8e8ca88d56c2d54f /clang/lib/Frontend/CompilerInvocation.cpp | |
| parent | 4fcdfc4398bdf9295cd0259d6416a7dc1d2da47f (diff) | |
| download | llvm-65d15fefe3392b1db2f679b3df029d43d8d26d2d.zip llvm-65d15fefe3392b1db2f679b3df029d43d8d26d2d.tar.gz llvm-65d15fefe3392b1db2f679b3df029d43d8d26d2d.tar.bz2 | |
[TargetList] Delete the destructor
AFAICT, ~TargetList simply implements the default destructor, plus some
locking.
The history is murky, so I'm not sure why we do this locking. Perhaps,
at some point, it was possible to delete the same TargetList instance
from two different threads, setting up a race. If that were true, then
the locking would protect against the race.
Since TargetList is uniquely owned by Debugger (m_target_list), no such
race is possible today.
Testing: check-lldb
Differential Revision: https://reviews.llvm.org/D90895
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions