------- Comment #4 from pluto at agmk dot net 2007-06-25 22:56 ------- (In reply to comment #2) > This is caused by two things, jump threading and inlining. If we jump thread > more, we no longer get the warning which is what you are seeing in 4.2.1. >
the latest gcc 4.2 also produces this warning. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32395