From: Xi Ruoyao <xry111@xry111.site>
To: Joseph Myers <joseph@codesourcery.com>
Cc: xuchenghua@loongson.cn, i.swmail@xen0n.name,
libc-alpha@sourceware.org, caiyinyu <caiyinyu@loongson.cn>
Subject: Re: [PATCH 1/1] LoongArch: Add pointer mangling support.
Date: Fri, 19 Aug 2022 21:46:37 +0800 [thread overview]
Message-ID: <e34d42b3accba112af7d8a49d0c2dc4c1d9d04c2.camel@xry111.site> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2208171643360.417173@digraph.polyomino.org.uk>
On Wed, 2022-08-17 at 16:46 +0000, Joseph Myers wrote:
> On Wed, 17 Aug 2022, Xi Ruoyao via Libc-alpha wrote:
>
> > I share your feeling... But the fix needed by ld.so (bc2a35c in
> > binutils-gdb.git) is after two commits massively changing the relocation
> > types. Backporting the relocation type changes is completely
> > unacceptable (such an attempt will do nothing except annoying Nick
> > Clifton :). And bc2a35c alone cannot be backported trivially.
>
> If the branch isn't usable as-is on LoongArch (which apparently is the
> state at present), there should be no problem with any backport to
> architecture-specific code, regardless of how large it is - it can't
> exactly regress from "not usable".
Sorry, my memory was flawed when I wrote the last reply (due to my 2-
week vacation :( ). It's not completely usable, only IFUNC is broken.
> I note that the only GCC target supported for LoongArch is
> loongarch*-*-linux*, so there isn't really a question of being usable for
> bare-metal either.
>
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-08-19 13:46 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
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 [this message]
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=e34d42b3accba112af7d8a49d0c2dc4c1d9d04c2.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).