------- Comment #5 from lloyd at randombit dot net 2007-11-16 02:00 ------- Argh, you are correct. The original code has
unsigned int n = an_input / 160; so this could never occur there, but GCC's inability to tell that this assignment means that n cannot be UINT_MAX (in that code) is clearly much like the original example. And then I simplified it enough that the loop actually could be infinite... Sorry for the noise. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34114
