public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danakj at orodu dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110999] New: GCC rejects static variable with constexpr storage from inline method definition
Date: Sat, 12 Aug 2023 04:44:26 +0000	[thread overview]
Message-ID: <bug-110999-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110999
           Summary: GCC rejects static variable with constexpr storage
                    from inline method definition
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: danakj at orodu dot net
  Target Milestone: ---

Godbolt: https://godbolt.org/z/srvhxjqqz

GCC will accept it if the method definition comes after the `constexpr` storage
definition. But it rejects it if the method definition is inline in the class.

```
struct OutOfLine {
    static const OutOfLine kConstant;
    constexpr int f();
    int i = 2;
};
inline constexpr OutOfLine OutOfLine::kConstant;
// Accepted.
constexpr int OutOfLine::f() { return kConstant.i; }

struct InLine {
    static const InLine kConstant;
    // Rejected.
    constexpr int f() { return kConstant.i; }
    int i = 2;
};
inline constexpr InLine InLine::kConstant;

int main() {
    constexpr int x = OutOfLine().f();
    constexpr int y = InLine().f();
}
```

                 reply	other threads:[~2023-08-12  4:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-110999-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).