This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Submission of a new gdb port
- To: gdb-patches at sourceware dot cygnus dot com
- Subject: Submission of a new gdb port
- From: Orjan Friberg <orjan dot friberg at axis dot com>
- Date: Mon, 02 Oct 2000 09:23:28 +0200
- Organization: Axis Communications AB
I am planning the submission of a new gdb port, and I would appreciate
some guidance as to the best procedure to do this.
The port is for an embedded system. The current status of the code is
that there are no deprecated macros, but I have not yet switched to the
multi-arch framework. During development, I used the 2000-05-19-release
source tree, but I just updated to the latest CVS sources.
* Will I be working with anyone in particular? Will the code be
scrutinized in the same way patches are?
* How stable is the multi-arch framework? Are there any catches
switching to it? (Will multi-arching allow me to debug APIs that only
differ in their respective sizes of a double?)
* Which currently supported target would be the best example for
architectural issues? Already being multi-arched, I reckon that the d10v
and the mn10300 are good candidates.
* Should I submit test results from the DejaGnu testsuite? Should I
submit patches for XFAILs specific to my target?
* The 4.18 port, on which the 5.0 port is heavily based, was developed
by another person at my company (for which an assign.future has been
submitted previously). How do I give proper credit to him?
Thanks for bearing with me on this.
--
Orjan Friberg E-mail: orjan.friberg@axis.com
Axis Communications AB Phone: +46 46 272 17 68