--- Comment #6 from manu at gcc dot gnu dot org 2010-06-06 16:41 ---
FIXED in GCC 4.6
--
manu at gcc dot gnu dot org changed:
What|Removed |Added
Status|NEW
--- Comment #5 from manu at gcc dot gnu dot org 2010-06-06 16:40 ---
Subject: Bug 2
Author: manu
Date: Sun Jun 6 16:40:18 2010
New Revision: 160346
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=160346
Log:
2010-06-06 Manuel López-Ibáñez
PR c/2
*
--- 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
--- Additional Comments From joseph at codesourcery dot com 2005-02-16
06:51 ---
Subject: Re: missing warning for noreturn function returning
non-void
On Wed, 16 Feb 2005, zack at codesourcery dot com wrote:
> ... because the attribute used to get translated to a volatile qualifier
>
--- Additional Comments From zack at codesourcery dot com 2005-02-16 06:48
---
... because the attribute used to get translated to a volatile qualifier
on the function type, iirc.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-16
06:45 ---
Confirmed, it is ovbious where the bug is if we look at the source:
/* GNU C interprets a volatile-qualified function type to indicate
that the function does not return. */
if ((t
