public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/8609: Superfluous warning when -std=c99/gnu99 and noreturn on main() Date: Mon, 25 Nov 2002 00:46:00 -0000 [thread overview] Message-ID: <20021119000611.24078.qmail@sources.redhat.com> (raw) The following reply was made to PR c/8609; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: Agthorr <agthorr@barsoom.org> Cc: bangerth@dealii.org, <141015@bugs.debian.org>, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Subject: Re: c/8609: Superfluous warning when -std=c99/gnu99 and noreturn on main() Date: Mon, 18 Nov 2002 18:04:56 -0600 (CST) On Mon, 18 Nov 2002, Agthorr wrote: > Well, I also compile with -Wmissing-noreturn. If I add the noreturn > attribute to main, gcc complains that the function returns. If I > remove the noreturn, gcc complains that the function does not return. > > gcc can't have it both ways. ;) However, if I remove the noreturn attribute line, I cannot make gcc complain about the code: tmp/g> cat x.c #include <stdlib.h> int main (void) { exit(1); } tmp/g> /home/bangerth/bin/gcc-3.3x-pre/bin/gcc -Wmissing-noreturn -std=gnu99 -c x.c tmp/g> What do you do differently? Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-11-19 0:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-25 0:46 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-25 7:16 bangerth 2002-11-24 17:24 Agthorr 2002-11-24 13:30 bangerth 2002-11-22 9:46 Matthias Klose
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20021119000611.24078.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).