public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mh+gcc at glandium dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53341] New: overloaded operator delete(void *) appear in object file even when not directly used Date: Mon, 14 May 2012 10:39:00 -0000 [thread overview] Message-ID: <bug-53341-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53341 Bug #: 53341 Summary: overloaded operator delete(void *) appear in object file even when not directly used Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: mh+gcc@glandium.org Consider the following program: ---------8<---------- #include <algorithm> extern void moz_free(void *ptr); __attribute__((always_inline)) inline void operator delete(void* ptr) throw() { return moz_free(ptr); } int foo() { return 42; } ---------8<---------- g++ -std=c++0x will put two symbols in the resulting object: _ZdlPv and _Z3foov. The former is operator delete(void *) This doesn't happen when including <new> instead of <algorithm>. This doesn't happen without -std=c++0x. This doesn't happen with operator new, operator new[], or operator delete[]. This doesn't happen when removing __attribute__((__externally_visible__)) from /usr/include/c++/4.7/new. (added in bug 50594)
next reply other threads:[~2012-05-14 10:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-14 10:39 mh+gcc at glandium dot org [this message] 2024-04-06 22:11 ` [Bug c++/53341] " pinskia at gcc dot gnu.org 2024-04-08 10:08 ` 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-53341-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).