From: Steve Underwood <steveu@coppice.org>
To: gdb@sources.redhat.com
Subject: New target support for GDB
Date: Wed, 24 Aug 2005 16:08:00 -0000 [thread overview]
Message-ID: <430C9B45.6030101@coppice.org> (raw)
Hi,
Support for the Texas Instruments MSP430 made its way into the main
binutils CVS some time ago. I kept letting the GDB support slip behind
the current changes, but now I am making a push to bring it up to date,
and get it into the main CVS. I have code that seems to work with this
week's GDB snaphot (6.3.50.20050822), though it needs more testing and
polishing before it is merged. I want to sort out the procedural stuff
in parallel with completing the code.
I understand I need to complete an FSF form, to contribute the code. I'm
not sure which form, or where I need to send it. I looked on the GNU
site, but there are a number of procedures for different circumstances.
I'd like to clarify the appropriate one. I don't know the procedure for
delivering the code, cleaning up anything which it not considered
appropriate, etc. Also, I don't know who the coordinator is, who would
deal with this.
Can someone help me?
We still need to get support into the main GCC repository. Once the GDB
stuff is in place, I will try to push the compiler stuff forward. We've
had solid support for GCC 3.2.3 since that was a new version. Again, we
haven't made the necessary push to catch up with changes to the compiler
core, and get our stuff merged. Now seems like a good time.
Regards,
Steve
next reply other threads:[~2005-08-24 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 16:08 Steve Underwood [this message]
2005-08-30 2:16 ` 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=430C9B45.6030101@coppice.org \
--to=steveu@coppice.org \
--cc=gdb@sources.redhat.com \
/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).