From: Jason Merrill <jason@redhat.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR debug/49348 (DW_TAG_template_* missing from template specializations)
Date: Fri, 10 Jun 2011 19:15:00 -0000 [thread overview]
Message-ID: <4DF2668F.30004@redhat.com> (raw)
In-Reply-To: <m3mxhpfs7u.fsf@redhat.com>
Hmm, I'm not sure about this; it seems to me that we want to know about
the actual parameters that a particular specialization has, which in the
case of an explicit specialization is none. Or for a partial
specialization,
template <class T> struct A;
template <class T> struct A<T*> { }
A<int*> a;
here A<int*> has a type parameter named T, with the value 'int'. It
would be very surprising for T to resolve to int* in the debugger when
it resolves to int in the body of A<T*>.
Which suggests that perhaps we want to leave the template arguments in
the name after all.
Jason
prev parent reply other threads:[~2011-06-10 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 18:40 Dodji Seketeli
2011-06-10 19:15 ` Jason Merrill [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=4DF2668F.30004@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@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).