c/3764: Gcc incorrectly complains that a noreturn function returns

[rth@gcc.gnu.org]

Synopsis: Gcc incorrectly complains that a noreturn function returns

Responsible-Changed-From-To: unassigned->rth
Responsible-Changed-By: rth
Responsible-Changed-When: Sun Jul 22 21:58:17 2001
Responsible-Changed-Why:
    Mine.
State-Changed-From-To: open->closed
State-Changed-By: rth
State-Changed-When: Sun Jul 22 21:58:17 2001
State-Changed-Why:
    Not a bug.  How can gcc possibly know that a write to a particular
    memory location resets the computer?  Either live with the
    warning, or fool the compiler by placing an infinite loop
    at the end of the function.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3764&database=gcc