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++/110437] SIGILL when return missing in a C++ function with a condition
Date: Tue, 27 Jun 2023 20:10:44 +0000	[thread overview]
Message-ID: <bug-110437-4-PXVfI4sBxh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110437-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110437

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The trap was added for PR 104642 because people keep ignoring the -Wreturn-type
warning and then complaining that the code misbehaves.

Of course now people complain that they prefer the unpredictable undefined
behaviour instead of predictable trapping.

You can't please everybody.

  parent reply	other threads:[~2023-06-27 20:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 17:03 [Bug c++/110437] New: " jan.zizka at nokia dot com
2023-06-27 17:13 ` [Bug c++/110437] " pinskia at gcc dot gnu.org
2023-06-27 17:19 ` pinskia at gcc dot gnu.org
2023-06-27 17:28 ` jan.zizka at nokia dot com
2023-06-27 17:30 ` pinskia at gcc dot gnu.org
2023-06-27 17:31 ` pinskia at gcc dot gnu.org
2023-06-27 17:46 ` jan.zizka at nokia dot com
2023-06-27 17:52 ` pinskia at gcc dot gnu.org
2023-06-27 18:02 ` jan.zizka at nokia dot com
2023-06-27 20:10 ` redi at gcc dot gnu.org [this message]
2023-06-27 20:22 ` jan.zizka at nokia dot com
2023-06-28  7:55 ` xry111 at gcc dot gnu.org
2023-06-28  8:02 ` jan.zizka at nokia dot com
2023-06-28  8:32 ` 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-110437-4-PXVfI4sBxh@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).