Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: gdb@sources.redhat.com
Subject: test
Date: Wed, 21 Mar 2001 15:59:00 -0000	[thread overview]
Message-ID: <20010323113336.A15082@redhat.com> (raw)

Is this group on?

cgf
From jtc@redback.com Wed Mar 21 15:59:00 2001
From: jtc@redback.com (J.T. Conklin)
To: GDB Discussion <gdb@sources.redhat.com>
Subject: Re: OBSOLETE GDB m68k platforms
Date: Wed, 21 Mar 2001 15:59:00 -0000
Message-id: <5msnkeua35.fsf@jtc.redback.com>
References: <3AB03EF5.FBB5ACF8@cygnus.com>
X-SW-Source: 2001-03/msg00133.html
Content-length: 821

>>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:
Andrew> As part of GDB 5.1, the following m68k platforms have been identified
Andrew> as candidates for obsolescence:
Andrew>
Andrew> 	m68*-isi-*
Andrew> 	m68*-sony-*

We might also want to consider removing:
        m68*-rom68k-*
        m68*-*bug-*

They all build, in fact they are all aliases to the generic embedded
m68k target.  If I recall corectly, these targets exist because back
in the pre-libgloss BSP days, newlib contained code for eval boards
with these ROM monitors so an entire separate toolchain (including
compiler, binutils, gdb, etc.) was built when only a tiny bit of code
was different.  

These are other aliases that don't make sense today:
        m68*-monitor-*
        m68*-est-*

        --jtc

-- 
J.T. Conklin
RedBack Networks


             reply	other threads:[~2001-03-21 15:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21 15:59 Christopher Faylor [this message]
2001-03-23  9:30 ` test Scott Bronson
2001-05-27 16:28 test Charles Wilkins
2001-07-04 23:11 test a_golzalmo_
2001-07-04 23:12 test a_golzalmo_
2001-07-04 23:12 test a_golzalmo_
2001-07-04 23:15 test a_golzalmo
2001-07-04 23:17 test argencorreo1
2001-07-04 23:18 test argencorreo
2001-07-04 23:23 test demo, newater
2001-08-08 17:44 test Wayne Ho

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=20010323113336.A15082@redhat.com \
    --to=cgf@redhat.com \
    --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