public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/49090] provide a way to recognize defaulted template parameters
Date: Fri, 01 Feb 2013 18:18:00 -0000 [thread overview]
Message-ID: <bug-49090-4-DVrbdgX9Fw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49090-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49090
--- Comment #7 from Tom Tromey <tromey at gcc dot gnu.org> 2013-02-01 18:18:01 UTC ---
(In reply to comment #6)
> What do you think about G++ (also) switching to emitting K<int> for DW_AT_name
> in this case? Would that break GDB type compatibility with other translation
> units that had K<int,int>?
Yeah, I think it may confuse name lookup in other cases.
For example, I think methods of this class will still appear
to be in K<int,int>, because that will still be baked into the
mangled form. So this would mean that finding a method's class
would fail.
Come to think of it I'm not sure how I will make "ptype K<int>"
work given the current state of gdb's symbol tables. Baby steps...
next prev parent reply other threads:[~2013-02-01 18:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 18:45 [Bug debug/49090] New: " tromey at gcc dot gnu.org
2011-05-20 20:16 ` [Bug debug/49090] " redi at gcc dot gnu.org
2013-01-31 19:59 ` jason at gcc dot gnu.org
2013-01-31 20:12 ` tromey at gcc dot gnu.org
2013-01-31 20:18 ` jason at gcc dot gnu.org
2013-01-31 20:26 ` tromey at gcc dot gnu.org
2013-02-01 17:58 ` jason at gcc dot gnu.org
2013-02-01 18:18 ` tromey at gcc dot gnu.org [this message]
2013-02-01 19:46 ` jason at gcc dot gnu.org
2013-02-01 19:48 ` jason at gcc dot gnu.org
2013-02-01 21:44 ` tromey at gcc dot gnu.org
2013-03-17 2:34 ` jason at gcc dot gnu.org
2014-07-15 14:05 ` redi at gcc dot gnu.org
2014-07-15 18:38 ` jason 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-49090-4-DVrbdgX9Fw@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).