From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Paul Eggert <eggert@cs.ucla.edu>, Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
debian-ia64@lists.debian.org, Matt Turner <mattst88@gmail.com>,
Sergei Trofimovich <slyfox@gentoo.org>
Subject: Re: RFC: Deprecate ia64 in glibc 2.34
Date: Tue, 2 Feb 2021 01:41:50 +0100 [thread overview]
Message-ID: <66284d2d-ee9d-867e-f38f-1057ad005dfc@physik.fu-berlin.de> (raw)
In-Reply-To: <c026ec40-79a4-473f-3773-c50a8b7c80e1@cs.ucla.edu>
Hello!
On 2/2/21 12:51 AM, Paul Eggert wrote:
> 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.
I think Sergei Trofimovich fixed some issues in the ia64 binutils after it was announced
the code was in danger. He is one of the Gentoo developers.
> 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 also have not heard from Jason for a while. I can try to contact him and find out what
the status is.
> I'll cc this email to debian-ia64 to see if anyone there has further info re GCC on ia64.
We should also pull in the Gentoo ia64 maintainers which I have done now.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2021-02-02 0:41 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
2021-02-02 0:41 ` John Paul Adrian Glaubitz [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=66284d2d-ee9d-867e-f38f-1057ad005dfc@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-ia64@lists.debian.org \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=mattst88@gmail.com \
--cc=slyfox@gentoo.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).