From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Harith George <mail2hgg@gmail.com>
Cc: Yuntao Liu <liuyuntao12@huawei.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, arnd@arndb.de, afd@ti.com,
linus.walleij@linaro.org, akpm@linux-foundation.org,
eric.devolder@oracle.com, masahiroy@kernel.org
Subject: Re: [PATCH] arm: Fix build issue with LD_DEAD_CODE_DATA_ELIMINATION
Date: Mon, 12 Aug 2024 16:06:35 +0100 [thread overview]
Message-ID: <Zrok+yGp5epfcZTE@shell.armlinux.org.uk> (raw)
In-Reply-To: <54f87fcb-74da-4b48-a12e-4c7d9fa2870e@gmail.com>
On Mon, Aug 12, 2024 at 01:21:59PM +0530, Harith George wrote:
> On 08-08-2024 18:05, 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/
>
> Build tested. Solves the earlier build issue I was seeing.
> fwiw, you can add my tested by tag if needed.
>
> Tested-by: Harith George <mail2hgg@gmail.com>
(a) please see the note in my signature below.
(b) this tested-by needs to be collected by the submitter before it gets
into the patch system.
(c) it needs to get into the patch system.
Bear in mind that as a result of (a), it's going to be better to get it
into the patch system sooner rather than later - I am expecting there to
be a period of time (weeks) where it will be impossible for me to read
the screen...
--
*** please note that I probably will only be occasionally responsive
*** for an unknown period of time due to recent eye surgery making
*** reading quite difficult.
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2024-08-12 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 12:35 [PATCH] arm: Fix build issue with LD_DEAD_CODE_DATA_ELIMINATION Yuntao Liu
2024-08-09 14:47 ` Arnd Bergmann
2024-08-12 7:51 ` Harith George
2024-08-12 15:06 ` Russell King (Oracle) [this message]
-- strict thread matches above, loose matches on Subject: below --
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=Zrok+yGp5epfcZTE@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=afd@ti.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=eric.devolder@oracle.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyuntao12@huawei.com \
--cc=mail2hgg@gmail.com \
--cc=masahiroy@kernel.org \
/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