public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ccoutant at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/64346] gcc generates incorrect debug info for ctor/dtor
Date: Fri, 19 Dec 2014 18:41:00 -0000 [thread overview]
Message-ID: <bug-64346-4-jSQynDE1zM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64346-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64346
--- Comment #4 from Cary Coutant <ccoutant at gcc dot gnu.org> ---
I think the problem is that the decloning turns the C1 and C2 ctors into
thunks, and GCC doesn't (yet) generate debug info for thunks, so when you
inline the C4 into the C1 or C2, and inline that into foo, all that's left in
the debug info is the inlined call to the C4 ctor.
It looks like -fno-declone-ctors-dtor doesn't work around the problem because
the "need_alias" flag is true, and that forces the decloning in this case.
The most expedient approach might be for you to alias the C4/D4 names to the
official ones when processing the profile data. Is that feasible?
prev parent reply other threads:[~2014-12-19 18:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 23:43 [Bug c++/64346] New: " dehao at gcc dot gnu.org
2014-12-17 23:45 ` [Bug c++/64346] " dehao at gcc dot gnu.org
2014-12-18 0:01 ` pinskia at gcc dot gnu.org
2014-12-18 0:05 ` dehao at gcc dot gnu.org
2014-12-19 18:41 ` ccoutant at gcc dot gnu.org [this message]
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-64346-4-jSQynDE1zM@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).