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++/107529] New: constexpr evaluator doesn't check for destroyed objects Date: Sat, 05 Nov 2022 01:04:23 +0000 [thread overview] Message-ID: <bug-107529-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107529 Bug ID: 107529 Summary: constexpr evaluator doesn't check for destroyed objects Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: vanyacpp at gmail dot com Target Milestone: --- I believe this function contains undefined behavior and should not be allowed to evaluate at compile-time. The call to `std::destroy_at(p)` should end the lifetime of `*p` and accesses to `*p` after that should be invalid. #include <memory> struct mytype { constexpr mytype() : x(42) {} constexpr ~mytype() {} int x; }; constexpr int foo() { std::allocator<mytype> alloc; mytype* p = alloc.allocate(1); std::construct_at(p); std::destroy_at(p); // destroy *p int result = p->x; // access alloc.deallocate(p, 1); return result; } static_assert(foo() == 42);
reply other threads:[~2022-11-05 1:04 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-107529-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).