From: Daniel Jacobowitz <drow@false.org>
To: Thomas Kuehne <thomas@kuehne.cn>
Cc: gdb-patches@sources.redhat.com
Subject: Re: D Symbol Demangling
Date: Thu, 20 Apr 2006 13:20:00 -0000 [thread overview]
Message-ID: <20060420132004.GB11710@nevyn.them.org> (raw)
In-Reply-To: <44462A40.1040004@kuehne.cn>
On Wed, Apr 19, 2006 at 02:17:04PM +0200, Thomas Kuehne wrote:
> Attached is a patch against GDB-6.4 that enables demangling of symbols
> generated by DMD[1] and GDC[2].
>
> The infrastructure part (c-lang.c, defs.h, d-lang.h, dwarf2read.c,
> language.c, Makefile.in, symfile, syntab.c, dwarf2.h) is based on John
> Demme's work[3][4].
>
> The pluggable demangler (gdb/demangle_d/*) was written completely form
> scratch and isn't based on John's work and supports templates and - to a
> certain extend - nested functions and types.
Unfortunately, there are several major problems with accepting this
code.
1. Neither you nor John has an FSF copyright assignment in place. If
you're interested in one, let me know and I can send you the forms.
2. The demangler would need to be contributed to the FSF and licensed
under the GPL before we could include it with GDB. That doesn't
prevent another copy of it from being used under a different license
elsewhere; but you wouldn't be able to import fixes from one to the
other, in either direction.
3. The code would need to match the GNU Coding Standards.
4. A patch would need to be generated against HEAD, not against an old
release.
And, no offense, but the DD_() thing is horribly ugly and doesn't seem
to serve any purpose here. Is that for reusing the demangler
elsewhere?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-20 13:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 11:18 Thomas Kuehne
2006-04-20 13:20 ` Daniel Jacobowitz [this message]
2006-04-20 15:20 ` OT: copyright issues (was: Re: D Symbol Demangling) Baurzhan Ismagulov
2006-04-20 15:40 ` DJ Delorie
2006-04-20 15:46 ` Daniel Jacobowitz
2006-04-20 16:39 ` Baurzhan Ismagulov
2006-04-20 17:05 ` Daniel Jacobowitz
2006-04-20 17:11 ` Baurzhan Ismagulov
2006-04-21 21:25 ` D Symbol Demangling Thomas Kühne
2006-04-22 22:52 ` Thomas Kühne
2006-04-24 17:21 ` Jim Blandy
2006-04-24 20:53 ` Daniel Jacobowitz
2006-04-25 3:35 ` Eli Zaretskii
2006-04-25 14:13 ` DJ Delorie
2006-04-29 7:23 ` Thomas Kühne
2006-04-29 16:47 ` DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
2005-04-04 2:37 John Demme
2005-04-04 18:21 ` Michael Snyder
2005-04-04 20:44 ` John Demme
2005-04-04 20:47 ` Daniel Jacobowitz
2005-04-04 21:49 ` Michael Snyder
2005-04-04 22:39 ` John Demme
[not found] ` <1112654359.14153.50.camel@localhost.localdomain>
[not found] ` <4251CF00.5080002@redhat.com>
2005-04-08 16:47 ` John Demme
2005-04-08 16:52 ` Daniel Jacobowitz
2005-04-08 20:50 ` John Demme
2005-04-08 21:11 ` Daniel Jacobowitz
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=20060420132004.GB11710@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=thomas@kuehne.cn \
/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