Dushistov marked an inline comment as done.
Dushistov added a comment.
> Should the leak be reported when the object is passed to
> QApplication::postEvent?
No, QApplication::postEvent == QCoreApplication::postEvent, it is just the same
function,
because of QApplication inherit from QCoreAppli
ABataev added a comment.
John, any comments?
http://reviews.llvm.org/D13336
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
zaks.anna accepted this revision.
zaks.anna added a comment.
This revision is now accepted and ready to land.
Thanks!
LGTM. I'll commit.
http://reviews.llvm.org/D14170
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi
zaks.anna added a comment.
This is a partial review. I did not look at the padding calculations closely.
Have you run this over codebases other than clang? Are there any false
positives?
> Even with the default of 8, this checker is too noisy to justify turning on
> by default. Clang+LLVM has
Author: pete
Date: Wed Nov 18 23:55:44 2015
New Revision: 253541
URL: http://llvm.org/viewvc/llvm-project?rev=253541&view=rev
Log:
Revert "Fix debian build after r253512."
This reverts commit r253519.
This likely broke the bots in
http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux2/builds/2
ygribov added inline comments.
Comment at: test/Analysis/inline.cpp:308
@@ +307,3 @@
+clang_analyzer_eval(0 != void_string); // expected-warning{{TRUE}}
+clang_analyzer_eval(0 != ((char *)void_string)[1]); //
expected-warning{{TRUE}}
+ }
zaks.anna wrote:
101 - 106 of 106 matches
Mail list logo