public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arthur.j.odwyer at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/92505] Using mutable in constexpr Date: Mon, 06 Sep 2021 16:28:14 +0000 [thread overview] Message-ID: <bug-92505-4-QQjyaEGp73@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-92505-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92505 Arthur O'Dwyer <arthur.j.odwyer at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arthur.j.odwyer at gmail dot com --- Comment #4 from Arthur O'Dwyer <arthur.j.odwyer at gmail dot com> --- Confirmed; the test case can be as simple as // https://godbolt.org/z/M9rf31qqq struct S { mutable int m; }; static_assert(S{42}.m == 42); (Removing the "mutable" keyword makes GCC happy.)
next prev parent reply other threads:[~2021-09-06 16:28 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-92505-4@http.gcc.gnu.org/bugzilla/> 2021-07-13 4:53 ` cjdb.ns at gmail dot com 2021-09-06 16:28 ` arthur.j.odwyer at gmail dot com [this message] 2022-09-15 18:04 ` ppalka at gcc dot gnu.org 2022-09-16 15:11 ` cvs-commit at gcc dot gnu.org 2022-09-18 16:58 ` ppalka 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-92505-4-QQjyaEGp73@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).