From: Alan Modra <amodra@bigpond.net.au>
To: Matt Thomas <matt@3am-software.com>
Cc: binutils@sources.redhat.com
Subject: Re: Unsupported targets slated for removal
Date: Tue, 22 Mar 2005 03:16:00 -0000 [thread overview]
Message-ID: <20050321231044.GL1260@bubble.modra.org> (raw)
In-Reply-To: <6.1.2.0.2.20050321134830.07564860@localhost>
On Mon, Mar 21, 2005 at 01:51:20PM -0800, Matt Thomas wrote:
> At 05:40 AM 3/21/2005, Alan Modra wrote:
> >I propose that the following targets be marked as unsupported in the
> >binutils 2.16 release, and be removed from mainline.
> >
> >
> >All non-BFD_ASSEMBLER gas targets. ie. the following, I think:
> >
> > vax-*-netbsd*
>
> vax-*-netbsdelf* is a BFD_ASSEMBLER target.
> Hence it should not be removed.
Right. That '*' matches more than I meant. If I listed cpu-*-netbsd*
as slated for removal, then I should have excepted cpu-*-netbsdelf*.
> > m88k-*-*
>
> Work is being done to bring this up to date, see
> http://mail-index.netbsd.org/port-m88k/2005/03/14/0000.html
Good. However, work in progress isn't enough to save m88k, I'm afraid.
m88k is currently a non-BFD_ASSEMBLER target, and I want to rip out all
the generic gas support for non-BFD_ASSEMBLER. I suppose we could keep
the m88k backend files on CVS head if the person working on m88k wanted,
but m88k-coff would no longer configure or build.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2005-03-21 23:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 15:35 Alan Modra
2005-03-22 1:11 ` Matt Thomas
2005-03-22 3:16 ` Alan Modra [this message]
2005-03-23 5:00 ` Mark Kettenis
2005-03-23 8:24 ` Alan Modra
2005-03-25 23:57 ` Mark Kettenis
2005-08-10 13:27 ` Alan Modra
2005-03-22 17:41 Christian Groessler
2005-03-23 9:28 ` Alan Modra
2005-08-10 13:51 Christian Groessler
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=20050321231044.GL1260@bubble.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=matt@3am-software.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).