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 1C2D33858C2D for ; Tue, 16 Aug 2022 01:30:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1C2D33858C2D Received: from [IPv6:240e:358:115c:cb00:dc73:854d:832e:2] (unknown [IPv6:240e:358:115c:cb00:dc73:854d:832e:2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-384)) (Client did not present a certificate) (Authenticated sender: xry111@xry111.site) by xry111.site (Postfix) with ESMTPSA id 8CA3B6686C; Mon, 15 Aug 2022 21:30:45 -0400 (EDT) Message-ID: <3740676145dbfab3595458d7a730272acd6fb928.camel@xry111.site> Subject: Re: [PATCH 1/1] LoongArch: Add pointer mangling support. From: Xi Ruoyao To: Joseph Myers , caiyinyu Cc: xuchenghua@loongson.cn, i.swmail@xen0n.name, libc-alpha@sourceware.org Date: Tue, 16 Aug 2022 09:30:40 +0800 In-Reply-To: References: <20220811040056.3164122-1-caiyinyu@loongson.cn> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.45.2 MIME-Version: 1.0 X-Spam-Status: No, score=-0.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: 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, 16 Aug 2022 01:30:54 -0000 On Mon, 2022-08-15 at 20:52 +0000, Joseph Myers wrote: > On Thu, 11 Aug 2022, caiyinyu wrote: >=20 > > Tested on LoongArch machine: gcc 13.0.0, Linux kernel 5.19.0 rc2, > > binutils branch master 2eb132bdfb9. >=20 > This appears to have broken the build-many-glibcs.py build ("Fatal error:= =20 > unknown reloc hint: pc_hi20").=C2=A0 Is that something that would be fixe= d by=20 > using binutils 2.39 branch instead of 2.38 branch in build-many-glibcs.py= ? No, we must use Binutils-2.40 for new relocation types like %pc_hi20.=20 Maybe we can add a configure check to fallback to "la.pcrel"/"la.got" macros for Binutils <=3D 2.39. --=20 Xi Ruoyao School of Aerospace Science and Technology, Xidian University