From: Michael Snyder <msnyder@cygnus.com>
To: Mark Byler <mbyler@maplenet.net>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: assignment forms
Date: Mon, 02 Apr 2001 13:20:00 -0000 [thread overview]
Message-ID: <3AC8DEEF.6CB81D5F@cygnus.com> (raw)
In-Reply-To: <3AC8DBF8.F20FEDE0@maplenet.net>
Mark Byler wrote:
>
> Michael Snyder wrote:
> >
> > Mark Byler wrote:
> > >
> > > Hello,
> > >
> > > I am looking into contributing to gdb sources. Your
> > > "Contributing to GDB" page talks about some documents like
> > > http://gcc.gnu.org/fsf-forms/assignment-instructions.html ,
> > > but this page does not exist.
> > >
> > > Is the copyright assignment really the first step? Should
> > > I talk to somebody about the kind of changes I want to
> > > contribute?
> >
> > The copyright assignment is an essential step, but not necessarily
> > the first. Jim Blandy (jimb@redhat.com) is your contact for the
> > copyright forms. If you'd like to discuss the changes you're
> > contemplating and look for feedback, this is an appropriate forum.
> > What did you have in mind?
> >
> > Michael
>
> I work with Kuck & Associates (KAI C++ compiler people)
> who recently were bought by Intel. KAI would like to make gdb
> the principal debugger for use with KAI C++, dropping an
> in-house debugger.
>
> KAI C++ uses an EDG front end. The changes we need are related
> to EDG style of compilation, which probably has broader application
> than just KAI C++. Specifically, we need
> - local variable demangling is slightly different, this
> is about a 20-line change in libiberty/cplus-dem.c
> - C++ baseclasses are represented differently, especially
> virtual baseclasses.
> - Digital alpha (aka axp/osf, tru64) does not know anything
> about baseclasses at all, as far as I can tell
> - might be some changes related to finding methods for classes
>
> This is not a complete list, but this is the sort of thing
> we are looking at. We would like to plow these changes back into
> the general source of gdb. On some platforms we might be interested
> in fixing some bugs. We might help get some ports done (I have a
> question out about 64-bit sparc).
>
> What do you think? Is this worth pursuing?
Of course. In your case, I'd recommend moving ahead on the assignment
forms right away, then you won't have that issue to wait on once you
have some concrete changes to submit.
next prev parent reply other threads:[~2001-04-02 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 7:26 Mark Byler
2001-04-02 11:18 ` Michael Snyder
2001-04-02 13:08 ` Mark Byler
2001-04-02 13:20 ` Michael Snyder [this message]
2001-04-02 13:43 ` Daniel Berlin
2001-05-21 14:51 ` Jim Blandy
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=3AC8DEEF.6CB81D5F@cygnus.com \
--to=msnyder@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=mbyler@maplenet.net \
/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