https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18487
--- Comment #16 from Eric Gallager <egallager at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #12) > And then there is the case of endless loops in such functions (either > unconditional, or ones the compiler is not able to detect), exit calls, both > either directly in the const/pure function or in some function it calls. So > in all, I'm afraid such a warning would diagnose only the most trivial cases. That would still be better than nothing.
