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 10A2438485B8 for ; Tue, 10 May 2022 19:37:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 10A2438485B8 Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-426-f-B_t6vyOjWMVv59Cr3jrg-1; Tue, 10 May 2022 15:37:38 -0400 X-MC-Unique: f-B_t6vyOjWMVv59Cr3jrg-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 023F180A0B9; Tue, 10 May 2022 19:37:38 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.113]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3E1E440C1421; Tue, 10 May 2022 19:37:36 +0000 (UTC) From: Florian Weimer To: caiyinyu Cc: libc-alpha@sourceware.org, xuchenghua@loongson.cn, joseph_myers@mentor.com Subject: Re: [PATCH v3 00/13] GLIBC LoongArch PATCHES References: <20220509022611.1248063-1-caiyinyu@loongson.cn> Date: Tue, 10 May 2022 21:37:34 +0200 In-Reply-To: <20220509022611.1248063-1-caiyinyu@loongson.cn> (caiyinyu@loongson.cn's message of "Mon, 9 May 2022 10:25:58 +0800") Message-ID: <8735hhb2m9.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.84 on 10.11.54.2 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-5.1 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, 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-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2022 19:37:45 -0000 > GCC and Binutils Loongarch parts have been into GNU Open Source community. > Loongarch kernal may be no problem on 5.19: It seems that the Linux 5.19 release date could be really close to the glibc 2.36 release date, or even after it. I think we wouldn't want to release with an ABI whose kernel interface is not in a mainline kernel yet. We have the option to backdate ABIs, so we could release the port with a GLIBC_2.36 ABI baseline in glibc 2.37. Or we could merge the port now, and back it out once more if Linux 5.19 does not get released in time. Maybe it's sufficient if the Linux port makes it to mainline during the 5.19 rc phase? Thoughts? Thanks, Florian