public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98675] New: Accessing member of temporary outside its lifetime allowed in constexpr function Date: Thu, 14 Jan 2021 11:53:09 +0000 [thread overview] Message-ID: <bug-98675-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98675 Bug ID: 98675 Summary: Accessing member of temporary outside its lifetime allowed in constexpr function Product: gcc Version: 10.2.1 Status: UNCONFIRMED Keywords: accepts-invalid Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org Target Milestone: --- struct X { int i = 0; constexpr int& get() { return i; } }; constexpr int g() { const auto& i = X{}.get(); return i; // undefined } constexpr auto i = g(); G++ fails to diagnose the error here. Clang says: <source>:13:16: error: constexpr variable 'i' must be initialized by a constant expression constexpr auto i = g(); ^ ~~~ <source>:10:12: note: read of object outside its lifetime is not allowed in a constant expression return i; // undefined ^ <source>:13:20: note: in call to 'g()' constexpr auto i = g(); ^ Intel says: <source>(13): error: expression must have a constant value constexpr auto i = g(); ^ <source>(10): note: attempt to access expired storage return i; // undefined ^
next reply other threads:[~2021-01-14 11:53 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-14 11:53 redi at gcc dot gnu.org [this message] 2021-01-14 14:31 ` [Bug c++/98675] " mpolacek at gcc dot gnu.org 2022-01-31 4:23 ` tobi at gcc dot gnu.org 2022-01-31 4:35 ` tobi at gcc dot gnu.org 2022-01-31 4:43 ` pinskia at gcc dot gnu.org 2022-01-31 11:44 ` tobi at gcc dot gnu.org 2023-05-26 15:00 ` pinskia at gcc dot gnu.org 2023-07-26 1:45 ` cvs-commit 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-98675-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).