From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 84EA33858418 for ; Mon, 14 Mar 2022 08:32:40 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 84EA33858418 Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-266-pU-gxhZpM-GH_CNtXvcRWQ-1; Mon, 14 Mar 2022 04:32:35 -0400 X-MC-Unique: pU-gxhZpM-GH_CNtXvcRWQ-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 83BC41C068D1; Mon, 14 Mar 2022 08:32:34 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.88]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D8FEE2157F34; Mon, 14 Mar 2022 08:32:32 +0000 (UTC) From: Florian Weimer To: "Joachim Schmitz" Cc: , , , "'Shiva Subramanian'" , "'Bill Honaker'" Subject: Re: AW: Re-port Intent for HPE NonStop (a.k.a. Tandem) References: <01ec01d836d7$f59d39a0$e0d7ace0$@nexbridge.com> <87k0cxynn8.fsf@oldenburg.str.redhat.com> <003901d8377b$32ab1e90$98015bb0$@schmitz-digital.de> Date: Mon, 14 Mar 2022 09:32:31 +0100 In-Reply-To: <003901d8377b$32ab1e90$98015bb0$@schmitz-digital.de> (Joachim Schmitz's message of "Mon, 14 Mar 2022 09:12:06 +0100") Message-ID: <87czipylwg.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H5, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-help@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-help mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2022 08:32:41 -0000 * Joachim Schmitz: > No idea whether that port had ever been send back upstream, it must have > been done in 2007 or before. > Not sure what you mean by "stable kernel interface"? In general, Linux does not remove any interfaces for entering the kernel once they have been added. The system call numbers that identify the entry points also does not change over time. For example, on x86-64, there is still a fstat system call, even though it has been superseded by newfstatat first, and then by statx. Other operating systems treat libc has the stable binary interface (if they have one at all), and remove the old system calls from their kernels once libc has been upgraded. This means it is not feasible to maintain libc as a separate project. > No, sorry, unfortunately no gcc available nor possible to cross-compile, it > is actually the assembler part that is missing IIRC You will have to release that first, preferably as a new target for binutils or LLVM, and then a compiler. But again, even if you do all that, it is unlikely that we would accept a glibc port. But without the toolchain, there is simply no way that it can happen. I think glibc stopped supporting proprietary toolchains some time in the 90s, before the glibc 2.0 release, and we are definitely not going back. Sorry. If you need a glibc compatibility layer, maybe you should look at gnulib instead. Thanks, Florian