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: Sun, 24 Nov 2002 13:30:00 -0000	[thread overview]
Message-ID: <20021118225507.26689.qmail@sources.redhat.com> (raw)

Synopsis: Superfluous warning when -std=c99/gnu99 and noreturn on main()

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Mon Nov 18 14:55:06 2002
State-Changed-Why:
    I can reproduce this. I think, the warning comes from the fact
    that in C99, main() has an implicit "return 0" at its end,
    indicating that if you fall off the end of main(), the
    programs return value is zero. This also explains why it
    only happens with main(), not if you rename the function.
    
    That being said, since you cannot control who calls main
    and how, what reason should you have to mark main() as
    noreturn? It should not make any difference, so why do
    it? I have difficulty seeing this as a bug...

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8609


             reply	other threads:[~2002-11-18 22:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-24 13:30 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-25  7:16 bangerth
2002-11-25  0:46 Wolfgang Bangerth
2002-11-24 17:24 Agthorr
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=20021118225507.26689.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: link
Be 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).