From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.74]) by sourceware.org (Postfix) with ESMTPS id A6C3F3858418 for ; Mon, 14 Mar 2022 08:49:40 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A6C3F3858418 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=schmitz-digital.de Authentication-Results: sourceware.org; spf=none smtp.mailfrom=schmitz-digital.de Received: from DodekaCore ([178.202.146.137]) by mrelayeu.kundenserver.de (mreue107 [213.165.67.113]) with ESMTPSA (Nemesis) id 1MMWcT-1njQn82jhv-00Jd42; Mon, 14 Mar 2022 09:49:21 +0100 From: "Joachim Schmitz" To: "'Florian Weimer'" Cc: , , , "'Shiva Subramanian'" , "'Bill Honaker'" References: <01ec01d836d7$f59d39a0$e0d7ace0$@nexbridge.com> <87k0cxynn8.fsf@oldenburg.str.redhat.com> <003901d8377b$32ab1e90$98015bb0$@schmitz-digital.de> <87czipylwg.fsf@oldenburg.str.redhat.com> In-Reply-To: <87czipylwg.fsf@oldenburg.str.redhat.com> Subject: AW: AW: Re-port Intent for HPE NonStop (a.k.a. Tandem) Date: Mon, 14 Mar 2022 09:49:20 +0100 Message-ID: <003c01d83780$66105e80$32311b80$@schmitz-digital.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQEXxrPuRx/llDaEPPRRpRc4hfKaWwFqVUXNAWf4yiYBd84PD64dH8/g Content-Language: de X-Provags-ID: V03:K1:udiiGhC/rc19a1CydDGV+0if8BqTWrpFu0lOqAXt+j/etPdJRG/ ilJEAONXlSJKpFSYyK5lISjc2tZ4TKG/xaebXVKfnX+PYTiSqafWbm6zQZmtMSyiAabFxjK pkMFghHuMTgr7bbKoxiYfFRVqks1XIlgWkGm9uui4v9UkQHj4vx/F+YGQaZNP56uYd5Li5p a3WHQmo4GqpjOSINfepYw== X-UI-Out-Filterresults: notjunk:1;V03:K0:tTJkrrq4ZBo=:PlbA0rdypHbS/NvnyVooKl 5nmGgxMW9ktw45r6sgVTYj63pZyZIOfWVCgVXtcPuE9xCQ83fTko/nN5cA56FvNO9Z0yxbCG2 yZ28IIgIKbzxAdWAOv+oCUHIXTGy0erg4cDl66VMQbEklJr0wXpp2gs8iFwwu9hnSE4QifrjU eAKMXyon274ew3UIYsthBTSn0TtRFXMKK7yDGbvNNAjSzyBjVAfpFd1XzYASrHQmVwwaOR9Um Gofhk9cmCuK0O/ypHn+irY9aLjjf1ye7uIANkX4BghzqpEeUmmSOj0Eb24vTXl5mtmtGW/C2k WO4pywQPxVYKR029elXow/Y7F/lATuph86h1ZiZHEFC15guT90Yk8VcdtOUOOF11ufyaOY5Xm eLjyXZ3Y36YNK9ArApNsqe/pdDxaJcEAzcsqTR69hVuy9cy1+2jKBg0u8a+3LQIna+1fxfPdw e5Qt5NVK9F8FZlJw9Iy0UmVLEbmJyATX41zbqqUqdTdJW7fyZMfKkYwLgCEocImZTFqGGD1TG AVyicBjcY/lhNSkU8GsE1TBKJ+befeBqajXEIt+OChcvTVNZup1N6JjiwGXkdQFM5YTIBZqSE tNOqbqbgBbtcjAAEiP85z5ViBDAU8zB2NcfP4N8qd/q7zyYXa04uAxao2BVs9+IPMEqh+xdcl q1xq+driWqFFEMO7mAItuFujIaN5EMVuqXaTztmH7jjoiqloZVfmgRl2vov3V+2o2Nvhi2/eQ Ajx6ObrmhICQ6Um5 X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no 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:49:42 -0000 Hi Florian OK, then in that sense NonStop Kernel is stable too Not sure what you'd expect us to "release first", out compiler? If so: sorry, that won't happen. We don't even own it ourself. If we were able to port gcc, I believe we'd not be allowed to share it, = due to proprietary code needed inside, needed to support the extension out platform needs. If glibc can't be made POSIX complaint, then that's where everything is = lost for us, as far as I can tell. But yes, we're using gnulib in places, and on top have our own = compatibility layer at some places. Bye, Jojo -----Urspr=FCngliche Nachricht----- Von: Florian Weimer =20 Gesendet: Montag, 14. M=E4rz 2022 09:33 An: Joachim Schmitz Cc: rsbecker@nexbridge.com; libc-help@sourceware.org; mike_kilpatrick@nskopensource.com; 'Shiva Subramanian' ; 'Bill Honaker' Betreff: Re: AW: Re-port Intent for HPE NonStop (a.k.a. Tandem) * Joachim Schmitz: > No idea whether that port had ever been send back upstream, it must=20 > 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=20 > 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