This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/12713] Document interaction of attribute noreturn and longjmp
- From: "user42 at zip dot com dot au" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 24 Oct 2003 21:24:57 -0000
- Subject: [Bug c/12713] Document interaction of attribute noreturn and longjmp
- References: <20031021211906.12713.user42@zip.com.au>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12713
------- Additional Comments From user42 at zip dot com dot au 2003-10-24 21:24 -------
Subject: Re: Document interaction of attribute noreturn and
longjmp
"bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> writes:
>
> While your reasoning is of course correct, a single sentence in the
> manual would clarify this without any doubt. I'd say, let's keep
> this open for now.
What I should have said in my first message was that it's the way
"abort" and "exit" are given as examples of noreturn functions that
plants the seed of doubt. It suggests, though without saying, that
noreturn is meant for cases where the function is going to terminate
the program (or thread presumably).