This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/34114] Missed optimization: cannot determine loop termination
- From: "lloyd at randombit dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 16 Nov 2007 02:00:43 -0000
- Subject: [Bug tree-optimization/34114] Missed optimization: cannot determine loop termination
- References: <bug-34114-6477@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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