public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "konstantin.vladimirov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/115233] New: constexpr RVO result is not determined as constant epression Date: Sun, 26 May 2024 12:16:17 +0000 [thread overview] Message-ID: <bug-115233-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115233 Bug ID: 115233 Summary: constexpr RVO result is not determined as constant epression Product: gcc Version: 14.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: konstantin.vladimirov at gmail dot com Target Milestone: --- Consider I have this type: --- struct Type { int a; const int& b; constexpr Type() : a(1), b(a) {} }; constexpr Type t1; constexpr int c11 = t1.a; constexpr int c12 = t1.b; --- c11 and c12 are fine for both gcc and clang Now lets introduce constexpr function which is subject to RVO: constexpr auto get() { return Type(); } Now try this: constexpr Type t2 = get(); constexpr int c2 = t2.a; This code compiles fine with clang but not with gcc. Live example on godbolt: https://godbolt.org/z/zf3YvebbG According to [expr.const] and [class.copy.elision] result of constexpr function is necessary RVO and is contant expression, so t2 construction is fine and t2.a is constant expression as well.
next reply other threads:[~2024-05-26 12:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-26 12:16 konstantin.vladimirov at gmail dot com [this message] 2024-05-26 12:18 ` [Bug c++/115233] " pinskia at gcc dot gnu.org 2024-05-26 12:20 ` pinskia 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-115233-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).