From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org, gdb@sourceware.org
Subject: Re: Support for alpha-osf, mips-irix
Date: Mon, 13 Jul 2020 13:11:04 +0200 [thread overview]
Message-ID: <yddwo37d60n.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <20200713104919.GG31072@bubble.grove.modra.org> (Alan Modra's message of "Mon, 13 Jul 2020 20:19:19 +0930")
Hi Alan,
> On Thu, Jul 09, 2020 at 04:21:54PM +0200, Rainer Orth wrote:
>> Every once in a while I come across references to Tru64 UNIX
>> (alpha*-dec-osf*)
>
> If you'd like to remove this config triple I think you could go ahead,
> but it doesn't buy us much really unless alpha-linuxecoff is also
> removed. I'm unsure as to how much use alpha-linuxecoff gets these
> days. Probably not much. It looks like it was removed from gcc in
> 2002.
indeed, just like MIPS/ECOFF. That's my point about those removals: if
there isn't a current version of GCC to support the targets, keeping
binutils support doesn't buy anyone a thing, not even the enthusiasts
that keep those machines alive.
One might include those targets in config.bfd's list of obsolete targets
on the 2.35 branch so potential remaining users get prominent notice
about the removal. Than at some point during the 2.36 cycle they could
be removed unless someone steps up to do the maintenance.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
prev parent reply other threads:[~2020-07-13 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 14:21 Rainer Orth
2020-07-12 2:08 ` Maciej W. Rozycki
2020-07-13 10:49 ` Alan Modra
2020-07-13 11:11 ` Rainer Orth [this message]
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=yddwo37d60n.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
/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).