public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@bigpond.net.au>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: binutils@sources.redhat.com
Subject: Re: Unsupported targets slated for removal
Date: Wed, 23 Mar 2005 08:24:00 -0000	[thread overview]
Message-ID: <20050322231328.GF30711@bubble.modra.org> (raw)
In-Reply-To: <200503222156.j2MLu0Qg029186@elgar.sibelius.xs4all.nl>

On Tue, Mar 22, 2005 at 10:56:00PM +0100, Mark Kettenis wrote:
>    Date: Tue, 22 Mar 2005 00:10:16 +1030
>    From: Alan Modra <amodra@bigpond.net.au>
> 
> Hi Alan,
> 
>    I propose that the following targets be marked as unsupported in the
>    binutils 2.16 release, and be removed from mainline.
> 
> What do you mean with "removed from mainline" here?  These targets

I want to kill all non-BFD_ASSEMBLER gas targets, to reduce the
maintenance burden, and allow BFD_ASSEMBLER gas targets to be cleaned up
without worrying about breaking the old code.  That will mean the
generic support code in gas for non-BFD_ASSEMBLER will disappear from
mainline.  Whether the corresponding tc-* files disappear or not doesn't
matter so much, but I favour complete removal.  You won't be able to
build these gas targets until they are converted over to use BFD.

More generally, I think we should remove targets that don't have active
maintainers listed in binutils/MAINTAINERS.  Again, this is simply to
reduce the maintenance burden.  Occasionally when making a global
change, I'd like to be able to email someone and say "xyz has changed,
please fix it for your target", rather than having to dig through some
crufty backend code myself.

> from your list:
> 
>        m88k-*-*
> 
>        vax-*-netbsd*
>        vax-*-bsd*
>        vax-*-ultrix*
> 
> are still fully supported by me in GDB, and support for them shouldn't
> be removed from bdf/ and opcodes/.

OK, I guess that's reasonable.  Please list yourself as a maintainer
in binutils/MAINTAINERS!

> Also putting my OpenBSD hat on, vax-*-elf is somewhat important to us,
> but from your reaction to Matt Thomass's mail you don't intend to
> whack that.

No.

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

  reply	other threads:[~2005-03-22 23:13 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
2005-03-23  5:00 ` Mark Kettenis
2005-03-23  8:24   ` Alan Modra [this message]
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=20050322231328.GF30711@bubble.modra.org \
    --to=amodra@bigpond.net.au \
    --cc=binutils@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    /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).