From: David Mosberger <davidm@napali.hpl.hp.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: davidm@hpl.hp.com, gcc@gcc.gnu.org, binutils@sources.redhat.com
Subject: Re: GNU DWARF augmentation authority
Date: Tue, 23 Nov 2004 23:09:00 -0000 [thread overview]
Message-ID: <16803.49267.19874.707422@napali.hpl.hp.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0411231739390.29669@dberlin.org>
>>>>> On Tue, 23 Nov 2004 17:41:20 -0500 (EST), Daniel Berlin <dberlin@dberlin.org> said:
Daniel> You want to email the dwarf2/3 committee reflector
>>
Daniel> Email Michael Eager at eager@eagercon.com.
>>
Daniel> He's the committee chair, and should be able to add you to
Daniel> the mailing list.
>> That's interesting. I thought the augmentation string used by
>> the GNU toolchain are purely a GNU extension. Is that not so?
Daniel> Depends on what you mean by "purely". If you mean we control
Daniel> them, then yes, they are purely GNU.
Daniel> However, i'm pretty sure they were discussed (as were other
Daniel> extensions) on the reflector before they were implemented,
Daniel> so as not to cause gratuitous problems with other
Daniel> extensions, etc.
Daniel> I'm sure Jason Merrill can correct me if i'm wrong about
Daniel> this.
Who would be the person(s) to decided whether the extensions are OK
for GNU? Since my (to be) proposed extension follow the GNU way of
interpreting the augmentation data, it seems to me that I should first
get approval (or at least a review/comments) for GNU first before
reaching out to the DWARF standard. Does that make sense?
--david
prev parent reply other threads:[~2004-11-23 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 22:29 David Mosberger
2004-11-23 22:37 ` Daniel Berlin
2004-11-23 22:56 ` David Mosberger
2004-11-23 22:58 ` Daniel Berlin
2004-11-23 23:09 ` David Mosberger [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=16803.49267.19874.707422@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=binutils@sources.redhat.com \
--cc=davidm@hpl.hp.com \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.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).