public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/43943] "warning: no return statement in function returning non-void" should be an error
Date: Fri, 30 Apr 2010 11:26:00 -0000	[thread overview]
Message-ID: <20100430112641.3669.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43943-19097@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from redi at gcc dot gnu dot org  2010-04-30 11:26 -------
The point being that it's undefined behaviour to /return/ from such a function,
not to /write/ such a function.

If the programmer guarantees the "missing return" will never happen then
there's no error.

I was wrong to say it's OK as long as the caller doesn't use the return value -
but it is OK as long as control never reaches the "missing return"


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43943


  parent reply	other threads:[~2010-04-30 11:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 20:13 [Bug c++/43943] New: " david at rothlis dot net
2010-04-29 20:32 ` [Bug c++/43943] " pinskia at gcc dot gnu dot org
2010-04-29 20:36 ` redi at gcc dot gnu dot org
2010-04-30  6:05 ` david at rothlis dot net
2010-04-30 11:22 ` redi at gcc dot gnu dot org
2010-04-30 11:26 ` redi at gcc dot gnu dot org [this message]
2010-04-30 14:01 ` david at rothlis dot net
     [not found] <bug-43943-4@http.gcc.gnu.org/bugzilla/>
2020-04-26  9:44 ` redi at gcc dot gnu.org
2022-04-19  9:55 ` kdevel at vogtner dot de
2023-03-31 18:38 ` pinskia at gcc dot gnu.org

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=20100430112641.3669.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).