2009/6/25 Richard Guenther <richard.guent...@gmail.com>: > On Thu, Jun 25, 2009 at 8:11 PM, Manuel > López-Ibáñez<lopeziba...@gmail.com> wrote: >> 2009/6/23 Ian Lance Taylor <i...@google.com>: >>> Paolo Bonzini <bonz...@gnu.org> writes: >>> >>>> I don't think this warning can report anything that -Wuninitialized >>>> cannot report, so it should go in -Wc++-compat only. >>> >>> For the record, it can, as in when compiling this case without >>> optimization. This is not a strong example by any means. >> >> This is a part of SSA that I don't understand completely. We create a >> var_decl for i in the following assignment: >> >> D.1606_1 = i; >> >> because i is loaded from memory. But then, because there is no alias >> info, there are no vuse/vdef operators for this statement. So we > > The only reason there is no VUSE/VDEF at -O0 is that we never need > it, so we omit it for efficiency reasons. We have enough information > at -O0 to add them should we need them.
My question was more like: Can we actually tell other way that this var_decl is an use of uninitialized variable? I think this is related to PR19430. Cheers, Manuel.
