public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marcpawl at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95772] New: warning desired when default operator= cannot be constructued Date: Fri, 19 Jun 2020 20:14:36 +0000 [thread overview] Message-ID: <bug-95772-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95772 Bug ID: 95772 Summary: warning desired when default operator= cannot be constructued Product: gcc Version: 10.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: marcpawl at gmail dot com Target Milestone: --- https://godbolt.org/z/eXckPe #include <type_traits> class Const { public: int const i_; Const(int i) : i_(i) {} Const& operator=(Const& rhs) = default; }; int main(int argc, char**) { Const c{argc}; static_assert(!std::is_assignable<Const, Const>::value, "should not be able to assign i_"); #ifdef ASSIGN Const d{argc + 1}; d = c; #endif return c.i_; } I expected a diagnostic saying that operator= cannot be defaulted which is seen if the ASSIGN code is enabled. The code compiles cleanly. When I wrote this bug in a large code base with -03 and -flto the code will fail with illegal instructions and other memory corruption errors. No problem without optimization.
next reply other threads:[~2020-06-19 20:14 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-19 20:14 marcpawl at gmail dot com [this message] 2020-06-19 20:30 ` [Bug c++/95772] " redi at gcc dot gnu.org 2020-06-19 23:59 ` marcpawl at gmail dot com 2020-06-20 14:28 ` redi at gcc dot gnu.org 2020-06-20 17:52 ` marcpawl at gmail dot com
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-95772-4@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).