Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Simon Richter <Simon.Richter@hogyros.de>
Cc: Richard Earnshaw <rearnsha@gcc.gnu.org>,
		Mark Mitchell <mark@codesourcery.com>,
	GDB <gdb@sources.redhat.com>
Subject: Re: ARM RDI
Date: Tue, 29 Nov 2005 17:54:00 -0000	[thread overview]
Message-ID: <20051129142714.GA23172@nevyn.them.org> (raw)
In-Reply-To: <438C6192.10109@hogyros.de>

On Tue, Nov 29, 2005 at 03:11:30PM +0100, Simon Richter wrote:
> Hi,
> 
> Daniel Jacobowitz wrote:
> 
> >>>1) Remove rdi-share from GDB entirely.
> 
> >>I think this one is probably best now...  I discussed it with Andrew at
> >>the Summit and we agreed it was the way to go.  But like dejagnu removal
> >>it's taking a long time to finally do it...
> 
> >Does anyone object?  If not, let's just do it.
> 
> For a number of CPUs, RDI is the only standard there is; it is the kind 
> of "obsolete" where they want people to buy their newer CPUs, not the 
> kind where there is a better standard. I'm fairly certain that there are 
> several trees where RDI works just fine as there are a number of 
> companies selling gdb based solutions for older ARM CPUs; the 
> interesting part will be getting those changes back from them.

There are a number of other ways to use RDI besides rdi-share.  I
believe Cygnus produced an RDI<->GDB conversion daemon and it may still
be available from Red Hat; I know CodeSourcery also ships such a
beast:

  http://www.codesourcery.com/gnu_toolchains/arm/faq.html#c_rdi

We're only talking about the in-tree copy of rdi-share, which is a
different beast alltogether.  I don't even think it works with some
current RDI targets.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  parent reply	other threads:[~2005-11-29 14:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-29  3:14 Mark Mitchell
2005-11-29 12:01 ` Richard Earnshaw
2005-11-29 14:12   ` Daniel Jacobowitz
2005-11-29 14:20     ` Simon Richter
2005-11-29 14:27       ` Richard Earnshaw
2005-11-29 17:54       ` Daniel Jacobowitz [this message]
2005-11-29 18:03         ` Mark Mitchell
2005-11-29 18:33           ` Daniel Jacobowitz
2005-11-29 18:52             ` Mark Mitchell
2005-12-09 17:24             ` Daniel Jacobowitz
2005-12-09 17:51               ` Simon Richter
2005-12-09 21:14               ` Stan Shebs
2005-11-29 18:49 ` Jim Blandy
2005-11-29 19:20   ` Mark Mitchell

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=20051129142714.GA23172@nevyn.them.org \
    --to=drow@false.org \
    --cc=Simon.Richter@hogyros.de \
    --cc=gdb@sources.redhat.com \
    --cc=mark@codesourcery.com \
    --cc=rearnsha@gcc.gnu.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