From: Yanteng Si <si.yanteng@linux.dev>
To: Wentao Guan <guanwentao@uniontech.com>, chenhuacai@kernel.org
Cc: kernel@xen0n.name, xry111@xry111.site, loongarch@lists.linux.dev,
linux-kernel@vger.kernel.org, wangyuli@uniontech.com,
zhanjun@uniontech.com
Subject: Re: [PATCH] LoongArch: vDSO: remove -nostdlib complier flag
Date: Wed, 30 Jul 2025 09:54:34 +0800 [thread overview]
Message-ID: <fd349fb6-be25-440e-932e-b15b6daedeee@linux.dev> (raw)
In-Reply-To: <20250725132651.1974717-1-guanwentao@uniontech.com>
在 7/25/25 9:26 PM, Wentao Guan 写道:
> It is clear to remove the -nostdlib for ld, it is similar to commit
> bdbf2038fbf4 ("MIPS: VDSO: remove -nostdlib compiler flag").
>
> Signed-off-by: Wentao Guan <guanwentao@uniontech.com>
Since MIPS has removed this, we should remove it too. In fact, other architectures also use $(LD).
fe00e50b2db8 ("ARM: 8858/1: vdso: use $(LD) instead of $(CC) to link VDSO")
691efbedc60d ("arm64: vdso: use $(LD) instead of $(CC) to link VDSO")
2ff906994b6c ("MIPS: VDSO: Use $(LD) instead of $(CC) to link VDSO")
2b2a25845d53 ("s390/vdso: Use $(LD) instead of $(CC) to link vDSO")
If Huacai is willing to apply this patch, I suggest supplementing the commit message.
Reviewed-by: Yanteng Si <siyanteng@cqsoftware.com.cn>
Thanks,
Yanteng
> ---
> arch/loongarch/vdso/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/loongarch/vdso/Makefile b/arch/loongarch/vdso/Makefile
> index ccd2c5e135c6..d8316f993482 100644
> --- a/arch/loongarch/vdso/Makefile
> +++ b/arch/loongarch/vdso/Makefile
> @@ -36,7 +36,7 @@ endif
>
> # VDSO linker flags.
> ldflags-y := -Bsymbolic --no-undefined -soname=linux-vdso.so.1 \
> - $(filter -E%,$(KBUILD_CFLAGS)) -nostdlib -shared --build-id -T
> + $(filter -E%,$(KBUILD_CFLAGS)) -shared --build-id -T
>
> #
> # Shared build commands.
next prev parent reply other threads:[~2025-07-30 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 13:26 Wentao Guan
2025-07-30 1:54 ` Yanteng Si [this message]
2025-07-30 7:25 ` Huacai Chen
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=fd349fb6-be25-440e-932e-b15b6daedeee@linux.dev \
--to=si.yanteng@linux.dev \
--cc=chenhuacai@kernel.org \
--cc=guanwentao@uniontech.com \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=wangyuli@uniontech.com \
--cc=xry111@xry111.site \
--cc=zhanjun@uniontech.com \
/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
Powered by JetHome