public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109364] Missing return statement in a non void function gives only a warning but produces a forced crash. Date: Fri, 31 Mar 2023 22:37:50 +0000 [thread overview] Message-ID: <bug-109364-4-9iePHiHx8S@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109364-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109364 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- As I will mention it again falling through from a function which has a non void return type is undefined. So gcc thinks it is unreachable. With the option is specify in comment #2, gcc 13 will cause a trap (usually an illegal instruction but could be an abort call). So there is nothing to change about gcc. Undefined code means just that if you invoke undefined code, anything can happen.
next prev parent reply other threads:[~2023-03-31 22:37 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-31 18:34 [Bug c++/109364] New: " contact at thunderperfectwitchcraft dot org 2023-03-31 18:38 ` [Bug c++/109364] " pinskia at gcc dot gnu.org 2023-03-31 18:40 ` pinskia at gcc dot gnu.org 2023-03-31 22:17 ` contact at thunderperfectwitchcraft dot org 2023-03-31 22:19 ` pinskia at gcc dot gnu.org 2023-03-31 22:21 ` contact at thunderperfectwitchcraft dot org 2023-03-31 22:37 ` pinskia at gcc dot gnu.org [this message] 2023-03-31 22:46 ` contact at thunderperfectwitchcraft dot org 2023-03-31 22:54 ` pinskia at gcc dot gnu.org 2023-03-31 22:57 ` redi at gcc dot gnu.org 2023-03-31 23:00 ` contact at thunderperfectwitchcraft dot org 2023-03-31 23:24 ` redi 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-109364-4-9iePHiHx8S@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: 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).