public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: caiyinyu <caiyinyu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, Joseph Myers <joseph@codesourcery.com>
Cc: xuchenghua@loongson.cn, i.swmail@xen0n.name, libc-alpha@sourceware.org
Subject: Re: [PATCH 1/1] LoongArch: Add pointer mangling support.
Date: Sun, 21 Aug 2022 15:25:57 +0800	[thread overview]
Message-ID: <68c4a0bc-7eb3-8f67-4b49-4a53119ef4a1@loongson.cn> (raw)
In-Reply-To: <e34d42b3accba112af7d8a49d0c2dc4c1d9d04c2.camel@xry111.site>


在 2022/8/19 下午9:46, Xi Ruoyao 写道:
> 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.

The ifunc supports are not available on binutils 2.39, so the ifunc tests

are failed. The " LoongArch: Add pointer mangling support" patch was tested

with ifunc disabled.

The full tests were all passed by using binutils master branch. If there

are no any other comments, I will include this patch.



>
>> 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.
>>


  reply	other threads:[~2022-08-21  7:26 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
2022-08-21  7:25               ` caiyinyu [this message]
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=68c4a0bc-7eb3-8f67-4b49-4a53119ef4a1@loongson.cn \
    --to=caiyinyu@loongson.cn \
    --cc=i.swmail@xen0n.name \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=xry111@xry111.site \
    --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).