From: Xi Ruoyao <xry111@xry111.site>
To: Joseph Myers <joseph@codesourcery.com>, caiyinyu <caiyinyu@loongson.cn>
Cc: xuchenghua@loongson.cn, i.swmail@xen0n.name, libc-alpha@sourceware.org
Subject: Re: [PATCH 1/1] LoongArch: Add pointer mangling support.
Date: Tue, 16 Aug 2022 09:30:40 +0800 [thread overview]
Message-ID: <3740676145dbfab3595458d7a730272acd6fb928.camel@xry111.site> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2208152050040.311521@digraph.polyomino.org.uk>
On Mon, 2022-08-15 at 20:52 +0000, Joseph Myers wrote:
> On Thu, 11 Aug 2022, caiyinyu wrote:
>
> > Tested on LoongArch machine: gcc 13.0.0, Linux kernel 5.19.0 rc2,
> > binutils branch master 2eb132bdfb9.
>
> This appears to have broken the build-many-glibcs.py build ("Fatal error:
> unknown reloc hint: pc_hi20"). Is that something that would be fixed by
> 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.
Maybe we can add a configure check to fallback to "la.pcrel"/"la.got"
macros for Binutils <= 2.39.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-08-16 1:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 4:00 caiyinyu
2022-08-15 20:52 ` Joseph Myers
2022-08-16 1:30 ` Xi Ruoyao [this message]
2022-08-16 1:59 ` Xi Ruoyao
2022-08-16 15:23 ` Joseph Myers
2022-08-17 7:43 ` Xi Ruoyao
2022-08-17 16:46 ` Joseph Myers
2022-08-19 13:46 ` Xi Ruoyao
2022-08-21 7:25 ` caiyinyu
2022-08-18 2:25 ` caiyinyu
2022-08-16 1:28 ` Xi Ruoyao
2022-08-16 6:34 ` caiyinyu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3740676145dbfab3595458d7a730272acd6fb928.camel@xry111.site \
--to=xry111@xry111.site \
--cc=caiyinyu@loongson.cn \
--cc=i.swmail@xen0n.name \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=xuchenghua@loongson.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).