From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from xry111.site (xry111.site [IPv6:2001:470:683e::1]) by sourceware.org (Postfix) with ESMTPS id 479EC3858407; Mon, 11 Jul 2022 16:06:52 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 479EC3858407 Received: from localhost.localdomain (xry111.site [IPv6:2001:470:683e::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-384) server-digest SHA384) (Client did not present a certificate) (Authenticated sender: xry111@xry111.site) by xry111.site (Postfix) with ESMTPSA id E518F669BB; Mon, 11 Jul 2022 12:06:47 -0400 (EDT) Message-ID: Subject: Re: glibc 2.36 - Slushy freeze (3 weeks to release) From: Xi Ruoyao To: Carlos O'Donell , libc-alpha Cc: caiyinyu , liuzhensong , binutils@sourceware.org, Wang Xuerui , Fangrui Song Date: Tue, 12 Jul 2022 00:06:45 +0800 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.3 MIME-Version: 1.0 X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FROM_SUSPICIOUS_NTLD, LIKELY_SPAM_FROM, PDS_OTHER_BAD_TLD, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: binutils@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Binutils mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2022 16:06:53 -0000 +binutils because we'll have to discuss binutils-related issues. On Mon, 2022-07-11 at 11:20 -0400, Carlos O'Donell via Libc-alpha wrote: > Desirable: >=20 > * GLIBC LoongArch PATCHES >=20 > The LoongArch patches are currently under review, but there looks to be > some unresolved binutils issues. Just for clarity we expect a glibc port > to have committed patches for the linux kernel, gcc, and binutils before > inclusion in glibc. GCC is mostly fine. There are some "outstanding" bugs in 12.1 but AFAIK they don't cause issues building glibc. You can use releases/gcc-12 branch if you have any doubt. Kernel userspace API is fine in 5.19-rc. There are issues about boot protocol and some drivers but these issues are completely unrelated to glibc. For binutils, ld is generating strange R_LARCH_NONE relocations (caused by an over-allocate of .rel.* sections and the usage of 0 as padding), and ld is generating R_LARCH_IRELATIVE for .rel.plt section (Fangrui says .rel.plt should not contain R_LARCH_IRELATIVE). Loongson engineers seems preparing a large patch series containing *both* the bug fix removing buggy R_LARCH_NONE and R_LARCH_IRELATIVE relocations, *and* the implementation of many new relocation types (superseding the current stack-based relocs which are disliked by many people, including me). Unfortunately, binutils 2.39 release branch is already created and I don't think such a large change set can be reviewed and landed into binutils soon. So I'll repeat my suggestion again: it's better to separate the bug fix and the new feature into two patch series, and get the bug fix landed and backported for binutils-2.39 branch ASAP. The new relocs (and/or other new features) can be reviewed later for binutils 2.40, after 2.39 release. I don't like the stack-based relocs, maybe even more than you guys - I remember I'd shout loudly with "colorful metaphors" when I had to use these relocs in LLVM. However another binutils release "supporting" LoongArch but completely unusable in practice will be worse. (Remind: 2.38 is already such a release.)