summaryrefslogtreecommitdiffstats
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2011-04-29 20:58:14 +0000
committerChandler Carruth <chandlerc@gmail.com>2011-04-29 20:58:14 +0000
commitf9e74104686126fd72228c4e489269d56ff1b54e (patch)
tree2f3d5fb53905d1edb2e6cec7a9d86befdcd8252d /clang/lib/Frontend/CompilerInvocation.cpp
parentc1f7c1d4696cd9ca6e43107a5cc6740b978740dd (diff)
downloadbcm5719-llvm-f9e74104686126fd72228c4e489269d56ff1b54e.tar.gz
bcm5719-llvm-f9e74104686126fd72228c4e489269d56ff1b54e.zip
Disable -Wnon-pod-memset for now while I try to reduce the false
positives still further. The plan is to: 1) Create a more targeted warning for memset of memory pointing at a type with virtual methods or bases where a vptr would be overwritten. 2) Consider turning the above warning back on by default. 3) Evaluate whether any false positives in the existing warning can be detected and white listed in the warning implementation. 4) If #3 lowers the noise floor enough, enable the full warning in -Wall or -Wextra. Comments or suggestions welcome. Even more welcome are specific test cases which trigger the warning and shouldn't. llvm-svn: 130538
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud