public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94470] New: Constexpr variable initialization with self-modifying constructor incorrectly rejected since r7-6728
Date: Fri, 03 Apr 2020 13:43:49 +0000	[thread overview]
Message-ID: <bug-94470-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 94470
           Summary: Constexpr variable initialization with self-modifying
                    constructor incorrectly rejected since r7-6728
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ppalka at gcc dot gnu.org
  Target Milestone: ---

$ cat testcase.C
struct X
{
  int b = 0;
  int c = ((this->b=1), 1);
};

constexpr X o = { };

static_assert(o.b == 1);

$ g++ -std=c++17 testcase.C
testcase.C:7:19: error: modification of ‘o’ is not a constant expression
 constexpr X o = { };
                   ^
testcase.C:9:19: error: non-constant condition for static assertion
 static_assert(o.b == 1);
               ~~~~^~~~

             reply	other threads:[~2020-04-03 13:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 13:43 ppalka at gcc dot gnu.org [this message]
2020-04-03 13:53 ` [Bug c++/94470] [8/9/10 Regression] " ppalka at gcc dot gnu.org
2020-04-03 13:57 ` mpolacek at gcc dot gnu.org
2020-04-03 13:57 ` mpolacek at gcc dot gnu.org
2020-04-13 12:11 ` ppalka at gcc dot gnu.org
2020-04-13 21:04 ` cvs-commit at gcc dot gnu.org
2020-04-13 21:06 ` [Bug c++/94470] [8/9 " ppalka at gcc dot gnu.org
2021-05-14  9:53 ` [Bug c++/94470] [9 " jakub at gcc dot gnu.org
2021-06-01  8:17 ` rguenth at gcc dot gnu.org
2022-05-27  8:51 ` rguenth 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-94470-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: 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).