lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a65d0b09-466d-415f-9bd0-cbc5ff3539e7@gmail.com>
Date: Wed, 7 Aug 2024 21:06:15 +0530
From: Harith George <mail2hgg@...il.com>
To: "liuyuntao (F)" <liuyuntao12@...wei.com>, arnd@...db.de,
 linus.walleij@...aro.org, rmk+kernel@...linux.org.uk, ardb@...nel.org,
 harith.g@...fsemi.com
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [build fail] v6.11-rc2 from "ARM: 9404/1: arm32: enable
 HAVE_LD_DEAD_CODE_DATA_ELIMINATION"



On 07-08-2024 20:52, liuyuntao (F) wrote:
> 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.
> 
Thanks for confirming.

I guess we need to add something like
#if !CONFIG_CC_IS_GCC || CONFIG_LD_VERSION >= 23600
around the entry-armv.S changes and maybe select 
HAVE_LD_DEAD_CODE_DATA_ELIMINATION in arch/arm/Kconfig only if the same 
conditions are met ??

I had screwed up the CC list when I last replied and LAK list got 
changed to lak-join email id by mistake. Fixing that in this reply as well.

Thanks,
Warm Regards,
Harith

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ