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++/100405] Add implicit 'return *this;' in assignment operators Date: Mon, 03 May 2021 22:22:34 +0000 [thread overview] Message-ID: <bug-100405-4-hbfrgRhszr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100405-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100405 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- Another option would be to add an implicit __builtin_trap() there. Failing hard is probably preferable to the kind of surprising behaviour you get from the optimizers today.
next prev parent reply other threads:[~2021-05-03 22:22 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-03 20:27 [Bug c++/100405] New: missing return assignment redi at gcc dot gnu.org 2021-05-03 20:28 ` [Bug c++/100405] " redi at gcc dot gnu.org 2021-05-03 20:40 ` [Bug c++/100405] Add implicit 'return *this;' in assignment operators redi at gcc dot gnu.org 2021-05-03 22:22 ` redi at gcc dot gnu.org [this message] 2021-05-03 22:38 ` jakub 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-100405-4-hbfrgRhszr@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).