From: Paul Eggert <eggert@cs.ucla.edu>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>, debian-ia64@lists.debian.org
Subject: Re: RFC: Deprecate ia64 in glibc 2.34
Date: Mon, 1 Feb 2021 15:51:25 -0800 [thread overview]
Message-ID: <c026ec40-79a4-473f-3773-c50a8b7c80e1@cs.ucla.edu> (raw)
In-Reply-To: <87r1lzoidk.fsf@oldenburg.str.redhat.com>
On 2/1/21 8:36 AM, Florian Weimer via Libc-alpha wrote:
> [PATCH] NEWS: Deprecate ia64-linux-gnu
> <https://sourceware.org/pipermail/libc-alpha/2021-January/122149.html>
>
> Consensus was not to deprecate the architecture, I think. But the
> binutils deprecation wasn't mentioned in the discussion.
I just now reviewed that thread, and in it Adhemerval mentioned
binutils' ia64 support as an argument for sticking with ia64 in glibc.
If binutils has deprecated, that argument goes away.
That thread also mentioned that Jason Duerstock volunteered in July 2019
to be the ia64 maintainer for GCC. However, although he submitted
copyright paperwork I don't see any commits by him in GCC master, and
the debian-ia64@lists.debian.org archive contains no email from him
since then, neither of which is a good sign.
I'll cc this email to debian-ia64 to see if anyone there has further
info re GCC on ia64.
next prev parent reply other threads:[~2021-02-01 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 15:05 H.J. Lu
2021-02-01 16:36 ` Florian Weimer
2021-02-01 23:51 ` Paul Eggert [this message]
2021-02-02 0:41 ` John Paul Adrian Glaubitz
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=c026ec40-79a4-473f-3773-c50a8b7c80e1@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=debian-ia64@lists.debian.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).