From: Doug Evans <dje@google.com>
To: Cary Coutant <ccoutant@google.com>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA] comdat types
Date: Fri, 26 Jun 2009 00:54:00 -0000 [thread overview]
Message-ID: <e394668d0906251754o8425642o77ad2c7f126dce98@mail.gmail.com> (raw)
In-Reply-To: <c17be2b30906251701s7cbe89a2h49dd416f470827c1@mail.gmail.com>
On Thu, Jun 25, 2009 at 5:01 PM, Cary Coutant<ccoutant@google.com> wrote:
>> I'm curious about one thing on this page, and I thought I'd take the
>> opportunity to ask. DW_TAG_type_unit may have a DW_AT_language child.
>> But, the language is not mentioned in the suggested method for
>> computing a type's signature. This seems strange to me: either the
>> language matters (in which case, it seems like it ought to be in the
>> signature); or the language does not matter, in which case, why
>> mention it?
>
> DW_AT_language was a late addition, and if I recall correctly, it was
> at Doug's request because there were still some places in gdb where
> the language mattered. It's an attribute of the type_unit (just like
> it is of the compile_unit), not of the type itself, so it's not
> involved in computing the type signature. Theoretically, if two type
> definitions from different languages generate the same signature,
> they're still the same type, and should be merged together. On the
> other hand, if the language really does matter to gdb, maybe they
> shouldn't be merged. I'm not sure it's likely enough to matter much,
> although I think it would be desirable for a C type and the same type
> in C++ to have the same signature. I had the impression that the
> dependence on language was a wart, and that ideally, it really
> shouldn't be necessary, so the language attribute is there only as
> helpful extra information.
I looked back, and apparently it there's by request of the dwarf committee.
Since it's there I made use of it, but that can change of course.
prev parent reply other threads:[~2009-06-26 0:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 0:04 Doug Evans
2009-06-25 19:47 ` Tom Tromey
2009-06-25 20:28 ` Doug Evans
2009-06-25 20:49 ` Tom Tromey
2009-07-15 1:13 ` Doug Evans
2009-07-15 19:28 ` Tom Tromey
2009-07-16 1:25 ` Doug Evans
2009-07-21 0:10 ` Cary Coutant
2009-06-26 1:33 ` Daniel Jacobowitz
2009-06-26 0:01 ` Cary Coutant
2009-06-26 0:54 ` Doug Evans [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=e394668d0906251754o8425642o77ad2c7f126dce98@mail.gmail.com \
--to=dje@google.com \
--cc=ccoutant@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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