Message ID | 87lfcbwvg8.fsf@oldenburg.str.redhat.com |
---|---|
State | Dropped |
Headers |
Return-Path: <libc-alpha-bounces@sourceware.org> X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id ED82F393BC0A; Fri, 29 Jan 2021 16:37:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ED82F393BC0A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1611938256; bh=qjUNUxqcs/xNKPLK5yxKLMc0DrAr9XH//bFz3qSq/Sk=; h=To:Subject:Date:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=maEidq49naaUHQgzV92l5XW9T9Ti1G9iE/ZdXBd2JAUXmzARIkEYbdHqIfWXmL/Px PgVdMZwIQL7U+ct91hzDXywkX4wVK5WWscHy3M4CaR2x15mjItz582qRcVecfdwJJA CL3zrA2qP3jvEZiKnGY0+L2Ewph2DhCk2BSTfS1Q= X-Original-To: libc-alpha@sourceware.org Delivered-To: libc-alpha@sourceware.org Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by sourceware.org (Postfix) with ESMTP id 1DDD3385803D for <libc-alpha@sourceware.org>; Fri, 29 Jan 2021 16:37:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 1DDD3385803D Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-318-SoaTVkR1OMqShmSXCVkvEg-1; Fri, 29 Jan 2021 11:37:31 -0500 X-MC-Unique: SoaTVkR1OMqShmSXCVkvEg-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 30FD0195D560 for <libc-alpha@sourceware.org>; Fri, 29 Jan 2021 16:37:30 +0000 (UTC) Received: from oldenburg.str.redhat.com (ovpn-113-35.ams2.redhat.com [10.36.113.35]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 8963819C66 for <libc-alpha@sourceware.org>; Fri, 29 Jan 2021 16:37:29 +0000 (UTC) To: libc-alpha@sourceware.org Subject: [PATCH] NEWS: Deprecate ia64-linux-gnu Date: Fri, 29 Jan 2021 17:37:27 +0100 Message-ID: <87lfcbwvg8.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-12.6 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, GIT_PATCH_0, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list <libc-alpha.sourceware.org> List-Unsubscribe: <https://sourceware.org/mailman/options/libc-alpha>, <mailto:libc-alpha-request@sourceware.org?subject=unsubscribe> List-Archive: <https://sourceware.org/pipermail/libc-alpha/> List-Post: <mailto:libc-alpha@sourceware.org> List-Help: <mailto:libc-alpha-request@sourceware.org?subject=help> List-Subscribe: <https://sourceware.org/mailman/listinfo/libc-alpha>, <mailto:libc-alpha-request@sourceware.org?subject=subscribe> From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org> Reply-To: Florian Weimer <fweimer@redhat.com> Errors-To: libc-alpha-bounces@sourceware.org Sender: "Libc-alpha" <libc-alpha-bounces@sourceware.org> |
Series |
NEWS: Deprecate ia64-linux-gnu
|
|
Commit Message
Florian Weimer
Jan. 29, 2021, 4:37 p.m. UTC
This reflects to the orpahned status of the ia64 architecture in the Linux kernel as of commit 96ec72a3425d1515b69b7f9dc34a4a6ce5862a37 ("ia64: Mark architecture as orphaned"). --- NEWS | 3 +++ 1 file changed, 3 insertions(+)
Comments
On 29/01/2021 13:37, Florian Weimer via Libc-alpha wrote: > This reflects to the orpahned status of the ia64 architecture in the > Linux kernel as of commit 96ec72a3425d1515b69b7f9dc34a4a6ce5862a37 > ("ia64: Mark architecture as orphaned"). I am not sure about this, the deprecation issue was also raised on gcc maillist and Jason step up to be the ia64 maintainer [1]. I also see that binutils does fix some ia64 issues from time to time. The Debian community still has working ia64 buildbots, which they gave access to test the latest releases. They can comment better their idea of the ia64-linux-gnu port. My take is once Linux is gone we are free to deprecate without a warning. [1] https://gcc.gnu.org/legacy-ml/gcc/2019-06/msg00150.html > > --- > NEWS | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/NEWS b/NEWS > index 01cbf282c3..782a6bd0e2 100644 > --- a/NEWS > +++ b/NEWS > @@ -84,6 +84,9 @@ Deprecated and removed features, and other changes affecting compatibility: > the baseline version (directly from the search path directory) will be > loaded. > > +* Support for the ia64-linux-gnu architecture is deprecated and will be > + removed from an upcoming glibc release. > + > Changes to build and runtime requirements: > > * On Linux, the system administrator needs to configure /dev/pts with >
* Adhemerval Zanella: > On 29/01/2021 13:37, Florian Weimer via Libc-alpha wrote: >> This reflects to the orpahned status of the ia64 architecture in the >> Linux kernel as of commit 96ec72a3425d1515b69b7f9dc34a4a6ce5862a37 >> ("ia64: Mark architecture as orphaned"). > > I am not sure about this, the deprecation issue was also raised on gcc > maillist and Jason step up to be the ia64 maintainer [1]. I also see > that binutils does fix some ia64 issues from time to time. > > The Debian community still has working ia64 buildbots, which they > gave access to test the latest releases. They can comment better their > idea of the ia64-linux-gnu port. > > My take is once Linux is gone we are free to deprecate without a > warning. Do you mean *remove* without further warning? Doesn't that itself a warning (as in, a deprecation)? Thanks, Florian
On 29/01/2021 14:02, Florian Weimer wrote: > * Adhemerval Zanella: > >> On 29/01/2021 13:37, Florian Weimer via Libc-alpha wrote: >>> This reflects to the orpahned status of the ia64 architecture in the >>> Linux kernel as of commit 96ec72a3425d1515b69b7f9dc34a4a6ce5862a37 >>> ("ia64: Mark architecture as orphaned"). >> >> I am not sure about this, the deprecation issue was also raised on gcc >> maillist and Jason step up to be the ia64 maintainer [1]. I also see >> that binutils does fix some ia64 issues from time to time. >> >> The Debian community still has working ia64 buildbots, which they >> gave access to test the latest releases. They can comment better their >> idea of the ia64-linux-gnu port. >> >> My take is once Linux is gone we are free to deprecate without a >> warning. > > Do you mean *remove* without further warning? > > Doesn't that itself a warning (as in, a deprecation)? The thing is I am not sure if someone would step up as ia64 maintainer for Linux. We have older architectures than ia64 with current upstream support. I have cc'ed the Debian developers responsible for the ia64 port, let see if they have any plan for the ia64 Linux support.
(CC'ing two of the Gentoo guys) Hi! On 1/29/21 5:51 PM, Adhemerval Zanella wrote: > On 29/01/2021 13:37, Florian Weimer via Libc-alpha wrote: >> This reflects to the orpahned status of the ia64 architecture in the >> Linux kernel as of commit 96ec72a3425d1515b69b7f9dc34a4a6ce5862a37 >> ("ia64: Mark architecture as orphaned"). > > I am not sure about this, the deprecation issue was also raised on gcc > maillist and Jason step up to be the ia64 maintainer [1]. I also see > that binutils does fix some ia64 issues from time to time. FWIW, the SH port of the Linux kernel was orphaned for a while as well until it found two new maintainers. So being orphaned in the kernel doesn't necessarily mean that a port is slated for removal. > The Debian community still has working ia64 buildbots, which they > gave access to test the latest releases. They can comment better their > idea of the ia64-linux-gnu port. Speaking for Debian, we're maintaining the port as good as possible but it's not in the best shape. glibc has many testsuite failures, ia64 support was removed with Ruby 2.7 and the ia64 backend gcc doesn't have a maintainer either. The Linux kernel for ia64 has issues on larger ia64 NUMA machines and doesn't boot there, smaller ia64 machines have issues with the hpsa driver currently which have been reported and the problematic commit been located, but the issue has not been resolved yet. So, if we want to continue to maintain the port, someone would at least need to fix the kernel issues. > My take is once Linux is gone we are free to deprecate without a > warning. I agree. But I'm interested to hear the voices from the Gentoo side. Adrian
diff --git a/NEWS b/NEWS index 01cbf282c3..782a6bd0e2 100644 --- a/NEWS +++ b/NEWS @@ -84,6 +84,9 @@ Deprecated and removed features, and other changes affecting compatibility: the baseline version (directly from the search path directory) will be loaded. +* Support for the ia64-linux-gnu architecture is deprecated and will be + removed from an upcoming glibc release. + Changes to build and runtime requirements: * On Linux, the system administrator needs to configure /dev/pts with