From: Richard Earnshaw <rearnsha@gcc.gnu.org>
To: Simon Richter <Simon.Richter@hogyros.de>
Cc: Daniel Jacobowitz <drow@false.org>,
Mark Mitchell <mark@codesourcery.com>,
GDB <gdb@sources.redhat.com>
Subject: Re: ARM RDI
Date: Tue, 29 Nov 2005 14:27:00 -0000 [thread overview]
Message-ID: <1133273985.32658.69.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <438C6192.10109@hogyros.de>
On Tue, 2005-11-29 at 14:11, 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.
It's also obsolete in the GNU sense of 'nobody has stepped up to
maintain the code'.
Are you volunteering?
R.
next prev parent reply other threads:[~2005-11-29 14:20 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 [this message]
2005-11-29 17:54 ` Daniel Jacobowitz
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=1133273985.32658.69.camel@pc960.cambridge.arm.com \
--to=rearnsha@gcc.gnu.org \
--cc=Simon.Richter@hogyros.de \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=mark@codesourcery.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