public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "de34 at live dot cn" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114078] New: operator new and operator delete are incorrectly acceptable as explicit object member functions Date: Fri, 23 Feb 2024 13:57:58 +0000 [thread overview] Message-ID: <bug-114078-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114078 Bug ID: 114078 Summary: operator new and operator delete are incorrectly acceptable as explicit object member functions Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: accepts-invalid Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: de34 at live dot cn Target Milestone: --- GCC currently accepts this wrong program while it shouldn't (https://godbolt.org/z/7jGnGqYPM), because member operator new/operator delete are always static member functions. #include <cstddef> #include <new> struct S { void* operator new(this std::size_t); void operator delete(this S*, std::destroying_delete_t); operator S*() const; operator std::size_t() const; }; int main() { S{}.operator new(); S{}.operator delete(std::destroying_delete); } Similar to https://github.com/llvm/llvm-project/issues/82249 which is fixed recently.
next reply other threads:[~2024-02-23 13:57 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-23 13:57 de34 at live dot cn [this message] 2024-02-23 17:47 ` [Bug c++/114078] " pinskia at gcc dot gnu.org 2024-04-23 6:00 ` cvs-commit at gcc dot gnu.org 2024-04-23 6:01 ` nshead 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-114078-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).