public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fchelnokov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110619] New: Dangling pointer returned from constexpr function converts in nullptr Date: Mon, 10 Jul 2023 18:39:36 +0000 [thread overview] Message-ID: <bug-110619-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110619 Bug ID: 110619 Summary: Dangling pointer returned from constexpr function converts in nullptr Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: fchelnokov at gmail dot com Target Milestone: --- The following function constexpr auto f() { int i = 0; return &i; }; returns dangling pointer on stack variable, but it is not nullptr. So next assertion passes in Clang and MSVC: static_assert( f() != nullptr ); But in GCC the assertion fails. Online demo: https://gcc.godbolt.org/z/6E4rE963n
next reply other threads:[~2023-07-10 18:39 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-10 18:39 fchelnokov at gmail dot com [this message] 2023-07-10 18:43 ` [Bug c++/110619] " pinskia at gcc dot gnu.org 2023-07-10 18:44 ` pinskia at gcc dot gnu.org 2023-07-10 19:04 ` fchelnokov at gmail dot com 2023-07-12 1:51 ` de34 at live dot cn 2023-07-13 19:02 ` ppalka at gcc dot gnu.org 2023-07-26 1:45 ` cvs-commit at gcc dot gnu.org 2023-08-07 5:04 ` peter at cordes dot ca 2023-08-07 7:41 ` fchelnokov at gmail dot com 2023-08-07 9:12 ` redi 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-110619-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).