From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: RFC: PR 9946 - template parameters
Date: Wed, 28 Jul 2010 15:38:00 -0000 [thread overview]
Message-ID: <m3fwz3obuu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100727214708.GA5432@caradoc.them.org> (Daniel Jacobowitz's message of "Tue, 27 Jul 2010 17:47:11 -0400")
>>>>> "Daniel" == Daniel Jacobowitz <dan@codesourcery.com> writes:
Daniel> I have no idea how this is going to interact with my patch to
Daniel> calculate template names when the compiler leaves out arguments from
Daniel> DW_AT_name; Pedro was looking at that, I think. But you've got the
Daniel> moral advantage since you posted this :-)
:)
Not putting the arguments in DW_AT_name actually seems cleaner to me.
GCC is still not emitting everything, though, so I don't think we could
make it do that yet.
Daniel> I like a 14-bit field not at all. Is it that size to soak up all
Daniel> available bits?
Yeah, just to avoid making the struct bigger than needed.
I'll turn it into a plain old int.
Thanks for looking at this. I'm going to check it in today.
Tom
next prev parent reply other threads:[~2010-07-28 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 23:02 Tom Tromey
2010-07-27 21:47 ` Daniel Jacobowitz
2010-07-28 15:38 ` Tom Tromey [this message]
2010-07-30 18:09 ` Pedro Alves
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=m3fwz3obuu.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.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).