mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "liuyuntao (F)" <liuyuntao12@huawei.com>
To: Harith George <mail2hgg@gmail.com>, <arnd@arndb.de>,
	<linus.walleij@linaro.org>, <rmk+kernel@armlinux.org.uk>,
	<ardb@kernel.org>, <harith.g@alifsemi.com>
Cc: <linux-arm-kernel-join@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [build fail] v6.11-rc2 from "ARM: 9404/1: arm32: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATION"
Date: Wed, 7 Aug 2024 23:22:54 +0800	[thread overview]
Message-ID: <2812367a-49ad-4c88-8844-8f8493b15bbd@huawei.com> (raw)
In-Reply-To: <52518ac5-53bb-4c70-ba99-4314593129dc@gmail.com>

Thanks, I reproduce the link error with toolchain
gcc version 9.3.0
GNU ld (GNU Binutils) 2.33.1

with same gcc version, just upgrading ld version to 2.36.1, it does not 
segfault and build completes. there should be bugs in low version of ld,
and the ".reloc  .text, R_ARM_NONE, ." triggers that.


On 2024/8/7 19:51, Harith George wrote:
> 
> 
> On 07-08-2024 15:19, liuyuntao (F) wrote:
>> It seems to be ok with vexpress_defconfig in mainline tree v6.11-rc2,
>> I may need your .config/code file for further testing.
>>
> Please find attached minimal patches just for your testing. "make 
> ARCH=arm e7_defconfig; make ARCH=arm xipImage"
> 
> Thanks,
> Warm Regards,
> Harith

  reply	other threads:[~2024-08-07 15:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07  5:12 Harith George
2024-08-07  6:42 ` liuyuntao (F)
2024-08-07  9:49 ` liuyuntao (F)
2024-08-07 11:51   ` Harith George
2024-08-07 15:22     ` liuyuntao (F) [this message]
2024-08-07 15:36       ` Harith George
2024-08-07 15:41         ` Arnd Bergmann
2024-08-07 15:47           ` liuyuntao (F)
2024-08-07 15:48           ` Harith George
2024-08-08  8:43             ` liuyuntao (F)
2024-08-08  8:31           ` liuyuntao (F)
2024-08-07 10:10 ` Arnd Bergmann
2024-08-07 11:21   ` Harith George

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=2812367a-49ad-4c88-8844-8f8493b15bbd@huawei.com \
    --to=liuyuntao12@huawei.com \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=harith.g@alifsemi.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel-join@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail2hgg@gmail.com \
    --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®