public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/96181] Missing return statement now leads to crashes
Date: Mon, 13 Jul 2020 11:26:10 +0000 [thread overview]
Message-ID: <bug-96181-4-2NIYTdABaP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96181-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96181
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Arturo Laurenzi from comment #0)
> Now, I understand the code snipped is probably broken. However, this change
> breaks old code that would work just fine by ignoring the undefined return
> value.
It didn't work fine, it had undefined behaviour. It just appeared to work fine.
GCC clearly warns you about it:
96181.C: In function ‘bool func(int)’:
96181.C:9:1: warning: no return statement in function returning non-void
[-Wreturn-type]
9 | } // missing return statement
| ^
If you're ignoring such warnings routinely maybe you should use
-Werror=return-type to force yourself to fix them.
next prev parent reply other threads:[~2020-07-13 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 10:40 [Bug c++/96181] New: " arturo.laurenzi at gmail dot com
2020-07-13 10:50 ` [Bug c++/96181] " pinskia at gcc dot gnu.org
2020-07-13 10:51 ` pinskia at gcc dot gnu.org
2020-07-13 11:26 ` redi at gcc dot gnu.org [this message]
2023-06-27 17:51 ` 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=bug-96181-4-2NIYTdABaP@http.gcc.gnu.org/bugzilla/ \
--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).