From: "Arnd Bergmann" <arnd@arndb.de>
To: "Yuntao Liu" <liuyuntao12@huawei.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: "Russell King" <linux@armlinux.org.uk>,
"Harith George" <mail2hgg@gmail.com>, "Andrew Davis" <afd@ti.com>,
"Russell King" <rmk+kernel@armlinux.org.uk>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Eric DeVolder" <eric.devolder@oracle.com>,
"Masahiro Yamada" <masahiroy@kernel.org>
Subject: Re: [PATCH] arm: Fix build issue with LD_DEAD_CODE_DATA_ELIMINATION
Date: Fri, 09 Aug 2024 16:47:41 +0200 [thread overview]
Message-ID: <b9aa586e-5685-4b5b-9732-81f2dec7120a@app.fastmail.com> (raw)
In-Reply-To: <20240808123556.681609-1-liuyuntao12@huawei.com>
On Thu, Aug 8, 2024, at 14:35, Yuntao Liu wrote:
> There is a build issue with LD segmentation fault, while
> CONFIG_LD_DEAD_CODE_DATA_ELIMINATION is not enabled, as bellow.
>
> scripts/link-vmlinux.sh: line 49: 3796 Segmentation fault
> (core dumped) ${ld} ${ldflags} -o ${output} ${wl}--whole-archive
> ${objs} ${wl}--no-whole-archive ${wl}--start-group
> ${libs} ${wl}--end-group ${kallsymso} ${btf_vmlinux_bin_o} ${ldlibs}
>
> The error occurs in older versions of the GNU ld with version earlier
> than 2.36. It makes most sense to have a minimum LD version as
> a dependency for HAVE_LD_DEAD_CODE_DATA_ELIMINATION and eliminate
> the impact of ".reloc .text, R_ARM_NONE, ." when
> CONFIG_LD_DEAD_CODE_DATA_ELIMINATION is not enabled.
>
> Fixes: ed0f94102251 ("ARM: 9404/1: arm32: enable
> HAVE_LD_DEAD_CODE_DATA_ELIMINATION")
> Reported-by: Harith George <mail2hgg@gmail.com>
> Suggested-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Yuntao Liu <liuyuntao12@huawei.com>
> Link:
> https://lore.kernel.org/all/14e9aefb-88d1-4eee-8288-ef15d4a9b059@gmail.com/
Looks good to me,
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2024-08-09 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 12:35 Yuntao Liu
2024-08-09 14:47 ` Arnd Bergmann [this message]
2024-08-12 7:51 ` Harith George
2024-08-12 15:06 ` Russell King (Oracle)
2024-08-12 7:57 Yuntao Liu
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=b9aa586e-5685-4b5b-9732-81f2dec7120a@app.fastmail.com \
--to=arnd@arndb.de \
--cc=afd@ti.com \
--cc=akpm@linux-foundation.org \
--cc=eric.devolder@oracle.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=liuyuntao12@huawei.com \
--cc=mail2hgg@gmail.com \
--cc=masahiroy@kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
/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
all inboxes | Powered by JetHome®