http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53871
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-07-07
07:11:23 UTC ---
(In reply to comment #0)
> Obvious endless loops could be reported, e.g. if the loop condition doesn't
> change and the loop can't be left otherwise.
There has been discussions about this since more than ten years ago and nothing
has happened:
http://gcc.gnu.org/ml/gcc/1999-08n/msg00720.html
My understanding is that the probability of an existing GCC dev implementing
this is very close to zero for various reasons: People are busy with other
things, not trivial to implement for non-trivial code, risk of being too noisy,
and there are other tools better at this job like splint and Clang's static
analyzer.
I can see some advantages in implementing this in GCC (sharing code, working in
any GCC FE), but those are not enough to make current developers drop what they
are doing and put time and effort on this.
So someone else will have to step up to the task. I suggest that you implement
it as a plugin and demonstrate that it works and it is not too noisy.
