public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: 141015@bugs.debian.org, agthorr@barsoom.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c/8609: Superfluous warning when -std=c99/gnu99 and noreturn on main() Date: Mon, 25 Nov 2002 07:16:00 -0000 [thread overview] Message-ID: <20021119011340.18186.qmail@sources.redhat.com> (raw) Synopsis: Superfluous warning when -std=c99/gnu99 and noreturn on main() State-Changed-From-To: analyzed->closed State-Changed-By: bangerth State-Changed-When: Mon Nov 18 17:13:39 2002 State-Changed-Why: Closed based on these comments: Date: Mon, 18 Nov 2002 16:30:10 -0800 From: Agthorr <agthorr@barsoom.org> To: Wolfgang Bangerth <bangerth@ticam.utexas.edu> Subject: Re: c/8609: Superfluous warning when -std=c99/gnu99 and noreturn on main() I was mistaken. gcc 2.95 complains when main() is not noreturn, which caused me to declare main() as noreturn. Later, I upgraded to gcc 3.0, which complains when main() is noreturn. The warning described in the original bug still seems wrong to me, but it's much less bothersome. I'll admit to being a perfectionist though ;) Date: Mon, 18 Nov 2002 17:10:48 -0800 From: Agthorr <agthorr@barsoom.org> To: Wolfgang Bangerth <bangerth@ticam.utexas.edu> Subject: Re: c/8609: Superfluous warning when -std=c99/gnu99 and noreturn on main() On Mon, Nov 18, 2002 at 06:46:42PM -0600, Wolfgang Bangerth wrote: > So am I right that you now have two switches for both compilers that give > you a warning on one but not the other, and omitting the right one on the > right compiler makes the warning go away? Yes. > If this is the case, I would suggest we close the report. I think, this is > such a corner case (main() being the only function for which an implicit > return is mandated), that it is hardly worth to think about it more if > there is a workaround. Fine by me. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8609
next reply other threads:[~2002-11-19 1:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-25 7:16 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-25 0:46 Wolfgang 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=20021119011340.18186.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=141015@bugs.debian.org \ --cc=agthorr@barsoom.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --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).