{"push_id":2419371324,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"8c99ee07d931d79b0a4aaf365ea7e1f7add7e9d2","before":"88f800cee89df21cca2aeafaa01f311f3921428f","commits":[{"sha":"8c99ee07d931d79b0a4aaf365ea7e1f7add7e9d2","author":{"name":"Artem Dergachev","email":"9c257a9f5889b207f966593fb6de1d6fc101973e@gmail.com"},"message":"[analyzer] Suppress more MallocChecker positives in smart pointer destructors.\n\nr326249 wasn't quite enough because we often run out of inlining stack depth\nlimit and for that reason fail to see the atomics we're looking for.\n\nAdd a more straightforward false positive suppression that is based on the name\nof the class. I.e. if we're releasing a pointer in a destructor of a \"something\nshared/intrusive/reference/counting something ptr/pointer something\", then any\nuse-after-free or double-free that occurs later would likely be a false\npositive.\n\nrdar://problem/38013606\n\nDifferential Revision: https://reviews.llvm.org/D44281","distinct":true,"url":"https://api.github.com/repos/llvm-project/llvm-project-submodule/commits/8c99ee07d931d79b0a4aaf365ea7e1f7add7e9d2"}]}
{"actor":{"display_login":"chapuni"}}