From: Andrew Cagney <ac131313@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb@sources.redhat.com
Subject: Re: [PATCH] Naming dwarves
Date: Tue, 20 May 2003 18:54:00 -0000 [thread overview]
Message-ID: <3ECA79CD.4090401@redhat.com> (raw)
In-Reply-To: <200305171253.h4HCrTT0012142@elgar.kettenis.dyndns.org>
> Andrew already made a side-remark in an earlier message: how are we
> going to name our files and functions related to DWARF?
>
> There are basically two generations of the DWARF Debugging Information
> Format. The first generation is usually referred to as DWARF Version
> 1. There is a 1.1.0 revision of the DWARF standard, but this revision
> is supposed to be fully binary compatible with the origional DWARF
> definition. The second generation is referred to as DWARF Version 2,
> or simply DWARF-2. Although the basic structure of Version 2 format
> is the very similar to Version 1, the encoding is different.
> Therefore these two formats are not binary compatible, which is why we
> have seperate DWARF and DWARF-2 symbol readers in GDB. There are also
> many new features in DWARF-2.
>
> There is also a public draft for DWARF Version 3, which should be
> largely binary compatible with Version 2. Standardization of Version
> 3 seems to have stopped, but some of the proposed extensions are
> already in use. I believe our DWARF-2 reader supports these. Since
> the Version 3 format is largely binary compatible with Version 2, I
> don't think we'll ever have a seperate DWARF-3 reader in GDB. The
> number of new features in the proposed standard is rather limited.
>
> Currently we have the following files dealing with DWARF:
>
> DWARF Version 1:
> dwarfread.c
>
> DWARF Version 2:
> dwarf2read.c
> dwarf2expr.c dwarf2expr.h
> dwarf2loc.c dwarf2loc.h
> dwarf2cfi.c dwarf2cfi.h (consider these deprecated)
> dwarf-frame.c dwarf-frame.h (on the i386newframe branch)
>
> The dwarfread.c module exports only one function:
> dwarf_build_psymtabs(). The dwarf2*.c modules export several
> functions, some with the dwarf2_ prefix, some with the dwarf_ prefix,
> and some with no prefix at all. I think Andrew would like to see that
> we use dwarf2 in the names of files implementing DWARF-2 things, and
> the dwarf2_ prefix for public function names. Is that right? If
> people agree, I'll rename my DWARF CFI bits before I move things over
> to mainline.
Yes, all correct, except ``DWARF 2'' (which appears in the spec once)
rather than ``DWARF-2'' :-)
Andrew
prev parent reply other threads:[~2003-05-20 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 12:53 Mark Kettenis
2003-05-18 4:35 ` Daniel Jacobowitz
2003-05-20 21:01 ` Jim Blandy
2003-05-19 13:07 ` James Cownie
2003-05-19 14:03 ` Elena Zannoni
2003-05-20 18:54 ` Andrew Cagney [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=3ECA79CD.4090401@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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).