Gitiles
Code Review Sign In
gerrit-public.fairphone.software / fp2-dev / platform / external / clang / d031c6aa0cb70000381b587574ce560ffbc59d00 / lib / Sema / AnalysisBasedWarnings.cpp
  1. 3078353 Per discussion on cfe-dev, re-enable suppression of -Wimplicit-fallthrough on C, but also include dialects of C++ earlier than C++11. by Ted Kremenek · 13 years ago
  2. 3e77351 Revert "Disable -Wimplicit-fallthrough when not using C++.", pending further discussion on cfe-dev. by Ted Kremenek · 13 years ago
  3. 6e3ceb5 Disable -Wimplicit-fallthrough when not using C++. by Ted Kremenek · 13 years ago
  4. c0e4445 -Warc-repeated-use-of-weak: allow single reads in loops from local variables. by Jordan Rose · 13 years ago
  5. b5cd122 -Warc-repeated-use-of-weak: Don't warn on a single read followed by writes. by Jordan Rose · 13 years ago
  6. 0bea863 StringRef-ify Binary/UnaryOperator::getOpcodeStr by David Blaikie · 13 years ago
  7. 1952354 Move the 'find macro by spelling' infrastructure to the Preprocessor class and by Dmitri Gribenko · 13 years ago
  8. 20441c5 Fix buildbots by not using a template from another namespace. by Jordan Rose · 13 years ago
  9. 66da0ab Compatibility macro detection for the -Wimplicit-fallthrough diagnostic. by Alexander Kornienko · 13 years ago
  10. 7a27048 -Warc-repeated-use-of-weak: check ivars and variables as well. by Jordan Rose · 13 years ago
  11. 58b6bdc Add a warning (off by default) for repeated use of the same weak property. by Jordan Rose · 13 years ago
  12. f3477c1 Revert 'Fix a typo 'iff' => 'if''. iff is an abreviation of if and only if. See: http://en.wikipedia.org/wiki/If_and_only_if Commit 164766 by Sylvestre Ledru · 13 years ago
  13. 94ff8e1 Fix a typo 'iff' => 'if' by Sylvestre Ledru · 13 years ago
  14. 5b280f2 Thread-safety analysis: fix ICE when EXCLUSIVE_LOCKS_REQUIRED or by DeLesley Hutchins · 13 years ago
  15. 3f0ec52 Thread-safety analysis: differentiate between two forms of analysis; a precise by DeLesley Hutchins · 13 years ago
  16. faadf48 Continue including temporary destructors in the CFG used for warnings. by Jordan Rose · 13 years ago
  17. df4ee10 [ms-inline asm] Remove old cruft now that MS-style asms their own code path. by Chad Rosier · 13 years ago
  18. 6cfa78f Uninitialized variables: two little changes: by Richard Smith · 13 years ago
  19. 879a433 Thread safety analysis: fixed incorrect error message at the end of a locks_required function. by DeLesley Hutchins · 13 years ago
  20. c2f51cf Stop referring to functions as methods in per-function fallthrough-checking. by Sean Hunt · 13 years ago
  21. 8cd64b4 Etch out the code path for MS-style inline assembly. by Chad Rosier · 13 years ago
  22. 1973634 Implementation of a "soft opt-in" option for -Wimplicit-fallthrough diagnostics: -Wimplicit-fallthrough-per-method by Alexander Kornienko · 13 years ago
  23. bdb97ff In response to some discussions on IRC, tweak the wording of the new by Richard Smith · 13 years ago
  24. a189d89 Don't offer '[[clang::fallthrough]];' fix-it when a fall-through occurs to a by Alexander Kornienko · 13 years ago
  25. 2815e1a Split a chunk of -Wconditional-uninitialized warnings out into a separate flag, by Richard Smith · 13 years ago
  26. 8189188 Some cleanups around the uninitialized variables warning, and a FIXME. No functional change. by Richard Smith · 13 years ago
  27. f6278e5 Pull some cases of initialization with self-reference warnings out of by Richard Trieu · 13 years ago
  28. 3bb2994 Silence unused-variable warning when assertions are disabled. by Kaelyn Uhrain · 13 years ago
  29. e0d3b4c Add -Wimplicit-fallthrough warning flag, which warns on fallthrough between by Richard Smith · 13 years ago
  30. 7b0a3e3 Fix a note without a SourceLocation. by Richard Trieu · 13 years ago
  31. 2c0abf4 Add FixItHint for -Wnull-conversion to initialize with an appropriate literal. by David Blaikie · 13 years ago
  32. d200187 [analyzer] Remove references to idx::TranslationUnit. Index is dead, cross-TU inlining never panned out. by Jordy Rose · 13 years ago
  33. ecafd30 ThreadSafetyReporter: Manage diagnostics in a std::list. by Benjamin Kramer · 13 years ago
  34. a34194f improve on diagnostic and provide a fixit hint when by Fariborz Jahanian · 13 years ago
  35. e4e68d4 When overload resolution picks an implicitly-deleted special member by Douglas Gregor · 13 years ago
  36. 793cd1c Specialize noreturn diagnostics for lambda expressions. by Douglas Gregor · 13 years ago
  37. d7a3e2c Revert my patches which removed Diagnostic.h includes by moving some operator overloads out of line. by Benjamin Kramer · 13 years ago
  38. 00bd44d Move various diagnostic operator<< overloads out of line and remove includes of Diagnostic.h. by Benjamin Kramer · 14 years ago
  39. 2e51562 Thread safety analysis: by Richard Smith · 14 years ago
  40. 23661d3 Revert various template unreachability code I committed accidentally. by David Blaikie · 14 years ago
  41. 36b7c63 Simple hack to do unreachable code analysis on template patterns. by David Blaikie · 14 years ago
  42. 71b8fb5 Make clang's AST model sizeof and typeof with potentially-evaluated operands correctly, similar to what we already do with typeid. by Eli Friedman · 14 years ago
  43. 7984de3 Improve 0-argument -Wvexing-parse diagnostic by adding notes with fix-its: by Richard Smith · 14 years ago
  44. 99ba9e3 Unweaken vtables as per http://llvm.org/docs/CodingStandards.html#ll_virtual_anch by David Blaikie · 14 years ago
  45. 1fa3c06 This patch extends thread safety analysis with support for the scoped_lockable attribute. by DeLesley Hutchins · 14 years ago
  46. 75df4ee Further tweak -Wurneachable-code and templates by allowing the warning to run on by Ted Kremenek · 14 years ago
  47. 5dfee06 Don't run -Wunreachable-code on template instantiations. Different instantiations may produce different unreachable code results, and it is very difficult for us to prove that ALL instantiations of a template have specific unreachable code. If we come up with a better solution, then we can revisit this, but this approach will at least greatly reduce the noise of this warning for code that makes use of templates. by Ted Kremenek · 14 years ago
  48. 1d26f48 Rename AnalysisContext to AnalysisDeclContext. Not only is this name more accurate, but it frees up the name AnalysisContext for other uses. by Ted Kremenek · 14 years ago
  49. b1b5daf [analyzer] Remove LocationContext creation methods from AnalysisManager, and change clients to use AnalysisContext instead. by Ted Kremenek · 14 years ago
  50. f1ac637 Thread safety analysis refactoring: invalid lock expressions. by DeLesley Hutchins · 14 years ago
  51. 0d38181 Only warn at self-initialization if some later use is always uninitialized. by Matt Beaumont-Gay · 14 years ago
  52. 9e76172 Tweak -Wuninitialized's handling of 'int x = x' to report that as the root cause of an uninitialized variable IFF there are other uses of that uninitialized variable. Fixes <rdar://problem/9259237>. by Ted Kremenek · 14 years ago
  53. fcdd2cb Don't suggest 'noreturn' for function template instantiations, because by Douglas Gregor · 14 years ago
  54. d6471f7 Rename Diagnostic to DiagnosticsEngine as per issue 5397 by David Blaikie · 14 years ago
  55. 4e4bc75 Thread safety: refactoring various out of scope warnings to use the same inteface. This eliminates a lot of unnecessary duplicated code. by Caitlin Sadowski · 14 years ago
  56. df8327c Thread safety: reverting to use separate warning for requirement to hold any lock by Caitlin Sadowski · 14 years ago
  57. e87158d Thread safety: Initializing var before exhaustive switch statement to deal with extraneous warning produced by gcc but not clang by Caitlin Sadowski · 14 years ago
  58. e05ee6d Switch -Wreturn-type to completely rely on the CFG model of no-return. by Chandler Carruth · 14 years ago
  59. 4f4f349 Show either a location or a fixit note, not both, for uninitialized variable warnings. by David Blaikie · 14 years ago
  60. b332109 Fix a diagnostics crasher with -Wmissing-noreturn in Objective-C by Douglas Gregor · 14 years ago
  61. 99107eb Thread safety: This patch deals with previously unhandled cases when building lock expressions. We now resolve this expressions, avoid crashing when encountering cast expressions, and have a diagnostic for unresolved lock expressions by Caitlin Sadowski · 14 years ago
  62. 402aa06 Thread Safety: Moving the analysis to a new file by Caitlin Sadowski · 14 years ago
  63. a49d1d8 Thread safety: refactoring test cases by Caitlin Sadowski · 14 years ago
  64. 75f23ae Thread safety: refactoring to use an error handler by Caitlin Sadowski · 14 years ago
  65. 179b920 Thread safety: small edit to unused variation on warning left in by accident from earlier commit by Caitlin Sadowski · 14 years ago
  66. 8bccabe Thread Safety: In C++0x Mutexes are the objects that control access to shared variables, while Locks are the objects that acquire and release Mutexes. We switch to this new terminology. by Caitlin Sadowski · 14 years ago
  67. af37061 Thread Safety: adding basic no thread safety analysis option by Caitlin Sadowski · 14 years ago
  68. 978191e Thread safety: Adding basic support for locks required and excluded attributes by Caitlin Sadowski · 14 years ago
  69. a53257c Thread safety: shared vs. exclusive locks by Caitlin Sadowski · 14 years ago
  70. eff98fc Thread Safety: Patch to implement delayed parsing of attributes within a by Caitlin Sadowski · 14 years ago
  71. b0656ec Improve the diagnostic text for -Wmissing-noreturn to include the name by Chandler Carruth · 14 years ago
  72. 05b436e Thread safety: added basic handling for pt_guarded_by/var and guarded_by/var annotations. We identify situations where we are accessing (reading or writing) guarded variables, and report an error if the appropriate locks are not held. by Caitlin Sadowski · 14 years ago
  73. b4d0a96 Thread safety: various minor bugfixes, with test cases by Caitlin Sadowski · 14 years ago
  74. cc68c9b In C++0x mode, suggest nullptr as the initializer for an uninitialized by Douglas Gregor · 14 years ago
  75. 940b97f Thread safety: Fix a few typos in last commit -- use LockID instead of Lock in comments and start a couple methods with a lowercase letter by Caitlin Sadowski · 14 years ago
  76. 0f3b4ca Start reworking -Wunreachable-code. The original analysis had serious flaws with how it by Ted Kremenek · 14 years ago
  77. f1d10d9 Constify the result of CFGStmt::getStmt(). by Ted Kremenek · 14 years ago
  78. 3ac1fbc Thread-safety analysis: adding in a basic lockset tracking system. This by Caitlin Sadowski · 14 years ago
  79. 5f9e272 remove unneeded llvm:: namespace qualifiers on some core types now that LLVM.h imports by Chris Lattner · 14 years ago
  80. d837c0d Move duplicate uninitialized warning suppression into the by Chandler Carruth · 14 years ago
  81. bc5cb8a Simplify passing of CFGBuildOptions around for AnalysisContext. No functionality change. by Ted Kremenek · 14 years ago
  82. 0c8e5a0 Reduce -Wuninitialized time by 22% (on sqlite) by removing the recursive AST crawl. by Ted Kremenek · 14 years ago
  83. 12efd57 Zero this struct in a way that neither depends on the size of the struct nor triggers warnings from GCC. by Benjamin Kramer · 14 years ago
  84. 57080fb Remove a gcc warning. by Fariborz Jahanian · 14 years ago
  85. 54cf341 Initialize all the AnalysisBasedWarnings statistics to zero. by Benjamin Kramer · 14 years ago
  86. 3ea4c49 Based on comments from Chris, switch to using CFG::getNumBlockIDs() by Chandler Carruth · 14 years ago
  87. 5d98994 Build up statistics about the work done for analysis based warnings. by Chandler Carruth · 14 years ago
  88. 8ba4426 When producing -Wuninitialized Fix-Its for pointers, prefer " = NULL" by Douglas Gregor · 14 years ago
  89. 1de8533 Teach CFG building how to deal with CXXMemberCallExprs and BoundMemberTy, by John McCall · 14 years ago
  90. 262d50e Simplify the tracking of when to issue a fixit hint, making the helper by Chandler Carruth · 14 years ago
  91. 64fb959 Separate the logic for issuing the initialization fixit hint from the by Chandler Carruth · 14 years ago
  92. 4c4983b Begin refactoring the uninitialized warning code that I uglied up. This by Chandler Carruth · 14 years ago
  93. b414c4f Fix PR9624 by explicitly disabling uninitialized warnings for direct self-init: by Chandler Carruth · 14 years ago
  94. 9f64946 Cleanup the style of some of this code prior to functional changes. by Chandler Carruth · 14 years ago
  95. d40066b Fix PR 9626 (duplicated self-init warnings under -Wuninitialized) with numerous CFG and UninitializedValues analysis changes: by Ted Kremenek · 14 years ago
  96. 6f41715 -Wuninitialized: use "self-init" warning when issue uninitialized values warnings from the dataflow analysis that include within the initializer of a variable. by Ted Kremenek · 14 years ago
  97. 5360c92 -Wuninitialized: don't issue fixit for initializer if a variable declaration already has an initializer. by Ted Kremenek · 14 years ago
  98. af13d5b Rename class 'CFGReachabilityAnalysis' to 'CFGReverseBlockReachabilityAnalysis'. by Ted Kremenek · 14 years ago
  99. c5e43c1 Don't construct two CFGs just to run -Wuninitialized. While this causes new warnings to be flagged under -Wconditional-uninitialized, this is something we by Ted Kremenek · 14 years ago
  100. 76709bf Split warnings from -Wuninitialized-experimental into "must-be-initialized" and "may-be-initialized" warnings, each controlled by different flags. by Ted Kremenek · 14 years ago