Diego Novillo wrote: > We won't get perfect answers, which is fine given the nature of the > problem. However, I would like, to get *consistent* answers.
Yes, I agree that's very important. In fact, I'd like to generalize that to say that -- as much as possible -- the same code should generate the same warnings across architectures, optimization levels, and releases as well. If -O3 causes us to say "might have been uninitialized, but we removed it" while -O0 just says "uninitialized" that's probably OK. But, having warnings not appear at -O0, or go away completely with higher levels of optimization isn't good. -- Mark Mitchell CodeSourcery, LLC [EMAIL PROTECTED] (916) 791-8304
