public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/58239] [4.9 regression] pretty-print.c:789: undefined reference to `operator delete(void*)'
Date: Sun, 25 Aug 2013 18:07:00 -0000 [thread overview]
Message-ID: <bug-58239-4-jbFjfg6z09@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58239-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58239
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Gabriel Dos Reis from comment #2)
> OK, I see the emitted reference to 'operator delete', and I suspect I
> have an idea of why the compiler generated this reference even though
> it isn't used anywhere in the input source code.
It is due to virtual deconstructors and in-charge vs out-of-charge
deconstructors happening.
next prev parent reply other threads:[~2013-08-25 18:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-58239-4@http.gcc.gnu.org/bugzilla/>
2013-08-25 17:07 ` gdr at gcc dot gnu.org
2013-08-25 18:07 ` pinskia at gcc dot gnu.org [this message]
2013-08-25 21:06 ` ebotcazou at gcc dot gnu.org
2013-08-25 21:55 ` gdr at gcc dot gnu.org
2013-08-26 0:23 ` gdr at gcc dot gnu.org
2013-08-28 9:18 ` rguenth at gcc dot gnu.org
2013-08-30 9:47 ` iains at gcc dot gnu.org
2013-08-30 14:24 ` gdr at gcc dot gnu.org
2013-08-30 14:54 ` iains at gcc dot gnu.org
2013-08-30 15:01 ` ebotcazou at gcc dot gnu.org
2013-08-30 15:07 ` gdr at gcc dot gnu.org
2013-08-31 21:21 ` ebotcazou at gcc dot gnu.org
2013-09-01 9:28 ` iains at gcc dot gnu.org
2013-09-01 9:49 ` ebotcazou at gcc dot gnu.org
2013-09-01 16:16 ` dominiq at lps dot ens.fr
2013-09-01 16:51 ` ebotcazou at gcc dot gnu.org
2013-09-01 16:54 ` ebotcazou at gcc dot gnu.org
2013-11-29 10:55 ` laguest at archeia dot com
2013-11-29 11:07 ` ebotcazou 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-58239-4-jbFjfg6z09@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: link
Be 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).