Summary: Seems it should have been done there all along. The analyzer does not currently understand the implementation of atomicity in folly::AtomicStruct. The analyzer does not currently understand when std::atomic operations are are used correctly versus incorrectly. The analyzer does not currently understand that the representation of folly::ThreadLocal is, ah, thread-local, leading to false alarms. The analyzer does not currently understand the control flow / scheduling constraints imposed by the implementation of Future. It seems that the implementation of folly::Optional is more C++ template magic than the analyzer can currently understand. The model of std::vector contains bogus memory accesses, leading to false alarms. Reviewed By: sblackshear Differential Revision: D6226199 fbshipit-source-id: 8cb083bmaster
parent
ce711d7e8a
commit
ec281799d5
Loading…
Reference in new issue