summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Transforms/Scalar/Reassociate.cpp
diff options
context:
space:
mode:
authorRichard Smith <richard-llvm@metafoo.co.uk>2012-05-26 06:20:46 +0000
committerRichard Smith <richard-llvm@metafoo.co.uk>2012-05-26 06:20:46 +0000
commit1bb8edb8acc00e1221ee3b8d6d9065eed05712b1 (patch)
tree8c64e2f9dc85f0dfb58ca622e73e2049faf0d1b2 /llvm/lib/Transforms/Scalar/Reassociate.cpp
parent3d8edc24c7dfde9fef86ec401b47181065c72ee6 (diff)
downloadbcm5719-llvm-1bb8edb8acc00e1221ee3b8d6d9065eed05712b1.tar.gz
bcm5719-llvm-1bb8edb8acc00e1221ee3b8d6d9065eed05712b1.zip
In response to some discussions on IRC, tweak the wording of the new
-Wsometimes-uninitialized diagnostics to make it clearer that the cause of the issue may be a condition which must always evaluate to true or false, rather than an uninitialized variable. To emphasize this, add a new note with a fixit which removes the impossible condition or replaces it with a constant. Also, downgrade the diagnostic from -Wsometimes-uninitialized to -Wconditional-uninitialized when it applies to a range-based for loop, since the condition is not written explicitly in the code in that case. llvm-svn: 157511
Diffstat (limited to 'llvm/lib/Transforms/Scalar/Reassociate.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud