From: Tom Tromey <tromey@redhat.com>
To: dje@google.com (Doug Evans)
Cc: binutils@sourceware.org, gcc-patches@gcc.gnu.org,
gdb-patches@sourceware.org, ccoutant@google.com
Subject: Re: [RFA] Add dwarf4 values to include/dwarf2.h
Date: Fri, 17 Jul 2009 00:02:00 -0000 [thread overview]
Message-ID: <m363ds8h2p.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090716205428.8CCBB846E6__41074.7728696608$1247777706$gmane$org@localhost> (Doug Evans's message of "Thu\, 16 Jul 2009 13\:54\:28 -0700 \(PDT\)")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> + DW_AT_GNU_odr_signature = 0x210f,
I would like to ask that all new GNU extensions be documented in
dwarf2.h. The existing extensions are already the subject of some
bafflement; I would like to end this practice.
I think my ideal form for this would be a long comment in the style of
the rest of the DWARF standard -- something that someone already
familiar with DWARF could readily read and understand.
Tom
next parent reply other threads:[~2009-07-16 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090716205428.8CCBB846E6__41074.7728696608$1247777706$gmane$org@localhost>
2009-07-17 0:02 ` Tom Tromey [this message]
2009-07-17 7:27 ` Doug Evans
2009-07-16 21:19 Doug Evans
2009-07-20 23:57 ` Doug Evans
2009-07-21 1:33 ` Ben Elliston
2009-07-21 1:35 ` Cary Coutant
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=m363ds8h2p.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=binutils@sourceware.org \
--cc=ccoutant@google.com \
--cc=dje@google.com \
--cc=gcc-patches@gcc.gnu.org \
--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