public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: Re: Can newlib drop old i960 and mn10200 targets?
Date: Wed, 27 Dec 2023 20:16:03 -0500	[thread overview]
Message-ID: <ZYzMU_JF2ERoGrWd@vapier> (raw)
In-Reply-To: <750a2d46-e376-45bc-b39c-9a9d549414ec@SystematicSW.ab.ca>

[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]

On 27 Dec 2023 10:07, Brian Inglis wrote:
> On 2023-12-26 22:47, Joel Sherrill wrote:
> > As the clean up patches for libgloss are coming by, I've checked a few to see 
> > when they disappeared from GCC. At least the i960 and mn10200 have been out of 
> > GCC for over a decade.
> > When should newlib remove them?
> 
> Maybe ask directly, as in subject, and in body ask, if not, when?

as Joel said, there are more targets than just those two.  i don't know that
debating them individually makes much sense.  having an agreed upon policy
and then seeing which arches it applies to is much easier.  if someone comes
out of the woodwork for a specific target and steps up to support it, then
maybe it can be postponed, but they'd be listed as a maintainer, and have to
respond to issues for it.

cr16 was dropped for the gcc-13 release.
crx was dropped for the gcc-4.7 release.
d30v was dropped for the gcc-4.0 release.
m68hc11 was dropped for the gcc-4.7 release.
mep was dropped for the gcc-7 release.
spu was dropped for the gcc-10 release.
xc16x has never been merged into gcc afaict.
-mike

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-12-28  1:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-27  5:47 When to remove old targets? Joel Sherrill
2023-12-27 17:07 ` Can newlib drop old i960 and mn10200 targets? Brian Inglis
2023-12-28  1:16   ` Mike Frysinger [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=ZYzMU_JF2ERoGrWd@vapier \
    --to=vapier@gentoo.org \
    --cc=newlib@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).