public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vanyacpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107161] gcc doesn't constant fold member if any other member is mutable
Date: Thu, 06 Oct 2022 12:39:02 +0000	[thread overview]
Message-ID: <bug-107161-4-gKBt2GIatq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107161-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Ivan Sorokin <vanyacpp at gmail dot com> ---
> Do constexpr/consteval work in such circumstances?

Yes, constexpr works for variables like "p.a":

extern constexpr mytype p = {1, 2};

int foo()
{
    constexpr int t = p.a + 10;
    return t;
}

foo():
        mov     eax, 11
        ret

https://godbolt.org/z/K9a69E4ar

      parent reply	other threads:[~2022-10-06 12:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 17:33 [Bug c++/107161] New: " vanyacpp at gmail dot com
2022-10-05 17:34 ` [Bug c++/107161] " pinskia at gcc dot gnu.org
2022-10-06 10:46 ` rguenth at gcc dot gnu.org
2022-10-06 12:39 ` vanyacpp at gmail dot com [this message]

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-107161-4-gKBt2GIatq@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).