Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stanshebs@google.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: delete target dbug/picobug/dink32/m32r/mon2000 ?
Date: Wed, 08 Jul 2015 18:59:00 -0000	[thread overview]
Message-ID: <CA+5-Q5JR-a07P4p+Wv+j8d+udXeNdXoUyoj1crLKsrYMdhbgzQ@mail.gmail.com> (raw)
In-Reply-To: <559D6FB0.9070103@redhat.com>

On Wed, Jul 8, 2015 at 11:45 AM, Pedro Alves <palves@redhat.com> wrote:
> All of these targets use gdb/monitor.c, which has bit rotted
> years ago (I'd guess around ~6), and nobody seems to
> have noticed.
>
> I propose deleting them (along with monitor.c):
>
> | target         | source               |
> |----------------+----------------------|
> | target dbug    | gdb/dbug-rom.c       |
> | target picobug | gdb/microblaze-rom.c |
> | target dink32  | gdb/dink32-rom.c     |
> | target m32r    | gdb/m32r-rom.c       |
> | target mon2000 | gdb/m32r-rom.c       |


I agree, that's an infrastructure whose time has come and gone.  (Not
much call for traditional ROM monitors when one can just as easily
boot to a real OS instead!) We would see references to people using
monitor backends from time to time, but I haven't seen any mentions
(with either new or old GDBs) in several years.

Stan


  reply	other threads:[~2015-07-08 18:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 18:45 Pedro Alves
2015-07-08 18:59 ` Stan Shebs [this message]
2015-07-08 19:10 ` Joel Sherrill
2015-07-08 19:27   ` Pedro Alves
2015-07-08 20:30     ` Michael Eager
2015-07-08 20:01   ` Stan Shebs

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=CA+5-Q5JR-a07P4p+Wv+j8d+udXeNdXoUyoj1crLKsrYMdhbgzQ@mail.gmail.com \
    --to=stanshebs@google.com \
    --cc=gdb@sourceware.org \
    --cc=palves@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