From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christopher Faylor <cgf@redhat.com>
To: gdb@sources.redhat.com
Subject: test
Date: Wed, 21 Mar 2001 15:59:00 -0000
Message-id: <20010323113336.A15082@redhat.com>
X-SW-Source: 2001-03/msg00237.html

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