------- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-26 01:13 ------- (In reply to comment #2) > I can imagine that it may not be straightforward to fix but I can't think of a > reason why a warning could ever be useful in this case (i.e., when the code is > provably safe). I could of course be missing something -- could you point me > to > the discussion where this was decided? Thanks!
Actually in 4.0.0 and above, it is an easy fix, just moving around the order around of the passes. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20644
