From: Cary Coutant <ccoutant@google.com>
To: Ben Elliston <bje@au1.ibm.com>
Cc: Doug Evans <dje@google.com>,
binutils@sourceware.org, gcc-patches@gcc.gnu.org,
gdb-patches@sourceware.org
Subject: Re: [RFA] Add dwarf4 values to include/dwarf2.h
Date: Tue, 21 Jul 2009 01:35:00 -0000 [thread overview]
Message-ID: <c17be2b30907201710n4eaff1a0h773a14788e7c2581@mail.gmail.com> (raw)
In-Reply-To: <1248134235.8878.0.camel@helios>
>> This patch adds various dwarf4 elements, plus DW_AT_GNU_odr_signature,
>> to include/dwarf2.h.
>
> Should this file even be called dwarf2.h any more?
DWARF-2 was so different from DWARF-1, it was essentially a new
format, so it made sense at the time. DWARF-3 and DWARF-4 are just
mostly-compatible extensions of DWARF-2, and updating the name for
each new revision would only be counterproductive. Just think of it as
"dwarf2+.h".
-cary
next prev parent reply other threads:[~2009-07-21 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
[not found] <20090716205428.8CCBB846E6__41074.7728696608$1247777706$gmane$org@localhost>
2009-07-17 0:02 ` Tom Tromey
2009-07-17 7:27 ` Doug Evans
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=c17be2b30907201710n4eaff1a0h773a14788e7c2581@mail.gmail.com \
--to=ccoutant@google.com \
--cc=binutils@sourceware.org \
--cc=bje@au1.ibm.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