[Bug tree-optimization/32759] False claim of that xyz is used uninitialized

2007-08-22 Thread manu at gcc dot gnu dot org
--- Comment #4 from manu at gcc dot gnu dot org 2007-08-22 16:49 --- Basically, when we reach diff = xlimit; we don't know that xlimit must be initialized. This may end up in different scenarios depending on the SSA tree finally generated. In any of those scenarios, not warning is sheer

[Bug tree-optimization/32759] False claim of that xyz is used uninitialized

2007-07-16 Thread bernard at brenda-arkle dot demon dot co dot uk
--- Comment #2 from bernard at brenda-arkle dot demon dot co dot uk 2007-07-16 19:01 --- I have gone through this removing many repetitions of see above for my actual bug report. Please take it as read (and see above for my actual bug report). I explicitly said that the mere

[Bug tree-optimization/32759] False claim of that xyz is used uninitialized

2007-07-16 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-07-16 19:10 --- Oh but what happens is we do some duplication of code (for 4.2 at least) and then we see the variable is used unitialization. This has changed in the trunk to a may used uninitialized but the issue is still the

[Bug tree-optimization/32759] False claim of that xyz is used uninitialized

2007-07-15 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-07-15 21:05 --- What is happening is that for the switch statement, we don't know that the value can't be just 0 or 1 at the point where we warn. We should be able to lower this switch statement into an if statement and get better