From: chenglulu <chenglulu@loongson.cn>
To: gcc-patches@gcc.gnu.org
Cc: xry111@xry111.site, i@xen0n.name, xuchenghua@loongson.cn,
lixing@loongson.cn, huajingyun@loongson.cn
Subject: Re:[pushed and backport] [PATCH] LoongArch: Modify MUSL_DYNAMIC_LINKER.
Date: Mon, 20 Nov 2023 10:29:43 +0800 [thread overview]
Message-ID: <5e968a98-a0fa-1d72-161b-fbb562204b7c@loongson.cn> (raw)
In-Reply-To: <20231118031513.31109-1-chenglulu@loongson.cn>
pushed to r14-5601
backport to r13-8085 and r12-9995.
r12 and r13 simultaneously synchronized the patch that changed '/lib64'
to '/lib'.
在 2023/11/18 上午11:15, Lulu Cheng 写道:
> Use no suffix at all in the musl dynamic linker name for hard
> float ABI. Use -sf and -sp suffixes in musl dynamic linker name
> for soft float and single precision ABIs. The following table
> outlines the musl interpreter names for the LoongArch64 ABI names.
>
> musl interpreter | LoongArch64 ABI
> --------------------------- | -----------------
> ld-musl-loongarch64.so.1 | loongarch64-lp64d
> ld-musl-loongarch64-sp.so.1 | loongarch64-lp64f
> ld-musl-loongarch64-sf.so.1 | loongarch64-lp64s
>
> gcc/ChangeLog:
>
> * config/loongarch/gnu-user.h (MUSL_ABI_SPEC): Modify suffix.
> ---
> gcc/config/loongarch/gnu-user.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/gcc/config/loongarch/gnu-user.h b/gcc/config/loongarch/gnu-user.h
> index 9616d6e8a0b..e9f4bcef1d4 100644
> --- a/gcc/config/loongarch/gnu-user.h
> +++ b/gcc/config/loongarch/gnu-user.h
> @@ -34,9 +34,9 @@ along with GCC; see the file COPYING3. If not see
> "/lib" ABI_GRLEN_SPEC "/ld-linux-loongarch-" ABI_SPEC ".so.1"
>
> #define MUSL_ABI_SPEC \
> - "%{mabi=lp64d:-lp64d}" \
> - "%{mabi=lp64f:-lp64f}" \
> - "%{mabi=lp64s:-lp64s}"
> + "%{mabi=lp64d:}" \
> + "%{mabi=lp64f:-sp}" \
> + "%{mabi=lp64s:-sf}"
>
> #undef MUSL_DYNAMIC_LINKER
> #define MUSL_DYNAMIC_LINKER \
prev parent reply other threads:[~2023-11-20 2:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 3:15 Lulu Cheng
2023-11-20 2:29 ` chenglulu [this message]
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=5e968a98-a0fa-1d72-161b-fbb562204b7c@loongson.cn \
--to=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=huajingyun@loongson.cn \
--cc=i@xen0n.name \
--cc=lixing@loongson.cn \
--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).