Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Svein E. Seldal" <Svein.Seldal@solidas.com>
To: Corey Minyard <minyard@acm.org>
Cc: gdb@sources.redhat.com
Subject: Re: Porting advice
Date: Mon, 31 Mar 2003 21:16:00 -0000	[thread overview]
Message-ID: <3E88B00B.3080905@solidas.com> (raw)
In-Reply-To: <3E888638.4060308@acm.org>

Corey Minyard wrote:
> You would save yourself a lot of work if you went to Google and type "TI 
> DSP gdb".
 >
 > It gives the following web site: http://www.elec.canterbury.ac.nz/c4x/

Thanks.

I am well aware of this page. In fact, all tic4x work is originating 
from that page/author. I am cooperating with Michael Hayes (the author) 
on this, and therefore I have become the binutils maintainer for the 
tic4x port; which mostly was based on his patches. What's found on this 
website is old and outdated.

Now, its time for me to look at gdb for this target. I have a tic4x 
patch for gdb from Michael. An old semi-working one, but I have one. My 
job now would be to adopt this patch to gdb HEAD (including things like 
multiarch and such). -- And eventually I intend to maintain the gdb port 
  together with binutils.

So here I am, needing to understand gdb. Thus all the questions....


Svein


  reply	other threads:[~2003-03-31 21:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 19:03 Svein E. Seldal
2003-03-28 22:56 ` Andrew Cagney
2003-04-03  9:23   ` Svein E. Seldal
2003-04-05  1:54     ` Andrew Cagney
2003-05-28 22:55       ` Porting advice or documentation request Svein E. Seldal
2003-05-29  9:49         ` Richard Earnshaw
2003-05-29 15:34           ` Elena Zannoni
2003-05-29 18:54             ` Andrew Cagney
2003-03-31 18:17 ` Porting advice Corey Minyard
2003-03-31 21:16   ` Svein E. Seldal [this message]
2003-03-31 22:36     ` Corey Minyard

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=3E88B00B.3080905@solidas.com \
    --to=svein.seldal@solidas.com \
    --cc=gdb@sources.redhat.com \
    --cc=minyard@acm.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