| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[analyzer][NFC] Move away from using raw-for loops inside StaticAnalyzer I'm involved with the Static Analyzer for the most part. I think we should embrace newer language standard features and gradually move forward. Differential Revision: https://reviews.llvm.org/D154325 | 2 年前 | |
[StaticAnalyzer] Stop including llvm/ADT/ImmutableMap.h (NFC) Identified with clangd. | 2 年前 | |
[clang][StaticAnalyzer] Avoid 'raw_string_ostream::str' (NFC) Since raw_string_ostream doesn't own the string buffer, it is desirable (in terms of memory safety) for users to directly reference the string buffer rather than use raw_string_ostream::str(). Work towards TODO comment to remove raw_string_ostream::str(). | 1 年前 | |
[analyzer] Adjust the reported variable name in retain count checker When reporting leaks, we try to attach the leaking object to some variable, so it's easier to understand. Before the patch, we always tried to use the first variable that stored the object in question. This can get very confusing for the user, if that variable doesn't contain that object at the moment of the actual leak. In many cases, the warning is dismissed as false positive and it is effectively a false positive when we fail to properly explain the warning to the user. This patch addresses the bigest issue in cases like this. Now we check if the variable still contains the leaking symbolic object. If not, we look for the last variable to actually hold it and use that variable instead. rdar://76645710 Differential Revision: https://reviews.llvm.org/D100839 | 5 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 5 年前 |