[llvm] r176341 - GCC thinks that this variable might be used uninitialized (it isn't).

[Chandler Carruth]

On Fri, Mar 1, 2013 at 1:46 AM, Duncan Sands <baldrick at free.fr> wrote:

> GCC thinks that this variable might be used uninitialized (it isn't).


Sorry to keep kicking the horse here, but I really oppose adding dead
stores to silence a broken warning.

We'll no longer be able to use Valgrind to catch a bug where the control
flow that intends to initialize this variable suddenly changes and fails to
do so in one case. =[ That seems really bad.

Clang's warnings don't have this false positive, and there is even a way to
silence GCCs in modern GCCs (-Wno-maybe-uninitialized) because of this
problem. Can we just turn off old GCC -Wuninitialized and rely on the
modern compilers' warnings instead?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130301/2db57c54/attachment.html>