This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/20000] missing warning for noreturn function returning non-void
- From: "manu at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 5 Aug 2009 13:55:34 -0000
- Subject: [Bug c/20000] missing warning for noreturn function returning non-void
- References: <bug-20000-230@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from manu at gcc dot gnu dot org 2009-08-05 13:55 -------
What happens when a function must have a particular return type because it is
accessed through a pointer, but we want to mark it as noreturn?
Example: gcc/java/jcf.h (jcf_unexpected_eof)
I am not sure this warning is all that useful as long as the function does not
have a return statement, and we already warn about this. I propose to remove
this warning altogether (less code, the same effect).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20000