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: Thu, 31 Jan 2013 20:12:00 -0000	[thread overview]
Message-ID: <bug-49090-4-Xlij4hYNVC@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 #3 from Tom Tromey <tromey at gcc dot gnu.org> 2013-01-31 20:11:36 UTC ---
(In reply to comment #2)
> Is GDB actually using the DW_TAG_template_*_param to generate the name of a
> type, or just using the pretty name generated by GCC for DW_AT_name?
> 
> Note that we don't currently generate those tags for uninstantiated types.

I don't think I understand this last comment.


A recent gdb does use the various template parameters to prettify
type display.  The example in this PR isn't so great, gdb gets
something wrong :(.  However:

(gdb) ptype k
type = struct K<int, int> [with T1 = int, T2 = int] {
    T1 v1;
    T1 v2;
}

I'd like to be able to print:

(gdb) whatis k
type = K<int>

This will make type display in various places more consistent with
what people generally want to see; and anyway there is an option to
peel back the curtain and see the full information.


  parent reply	other threads:[~2013-01-31 20:12 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 [this message]
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
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-Xlij4hYNVC@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).