All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Russell King <linux@armlinux.org.uk>,
	Nick Desaulniers <ndesaulniers@google.com>,
	soc@kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Tom Rix <trix@redhat.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
	Ard Biesheuvel <ardb@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] ARM: disallow pre-ARMv5 builds with ld.lld
Date: Fri, 16 Dec 2022 16:10:32 -0700	[thread overview]
Message-ID: <Y5z66Oh1mcOul0Jw@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20221215162635.3750763-1-arnd@kernel.org>

On Thu, Dec 15, 2022 at 05:26:20PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> lld cannot build for ARMv4/v4T targets because it inserts 'blx' instructions
> that are unsupported there:
> 
>   ld.lld: warning: lld uses blx instruction, no object with architecture supporting feature detected
> 
> Add a Kconfig time dependency to prevent those targets from being
> selected in randconfig builds.
> 
> Link: https://github.com/llvm/llvm-project/issues/50764
> Link: https://github.com/ClangBuiltLinux/linux/issues/964
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Reviewed-by: Nathan Chancellor <nathan@kernel.org>

> ---
>  arch/arm/Kconfig | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index 4a8fff7f9be0..d995054ab602 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -344,12 +344,14 @@ comment "CPU Core family selection"
>  config ARCH_MULTI_V4
>  	bool "ARMv4 based platforms (FA526, StrongARM)"
>  	depends on !ARCH_MULTI_V6_V7
> +	depends on !LD_IS_LLD
>  	select ARCH_MULTI_V4_V5
>  	select CPU_FA526 if !(CPU_SA110 || CPU_SA1100)
>  
>  config ARCH_MULTI_V4T
>  	bool "ARMv4T based platforms (ARM720T, ARM920T, ...)"
>  	depends on !ARCH_MULTI_V6_V7
> +	depends on !LD_IS_LLD
>  	select ARCH_MULTI_V4_V5
>  	select CPU_ARM920T if !(CPU_ARM7TDMI || CPU_ARM720T || \
>  		CPU_ARM740T || CPU_ARM9TDMI || CPU_ARM922T || \
> -- 
> 2.35.1
> 

WARNING: multiple messages have this Message-ID

From: Nathan Chancellor <nathan@kernel.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Russell King <linux@armlinux.org.uk>,
	Nick Desaulniers <ndesaulniers@google.com>,
	soc@kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Tom Rix <trix@redhat.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
	Ard Biesheuvel <ardb@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] ARM: disallow pre-ARMv5 builds with ld.lld
Date: Fri, 16 Dec 2022 16:10:32 -0700	[thread overview]
Message-ID: <Y5z66Oh1mcOul0Jw@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20221215162635.3750763-1-arnd@kernel.org>

On Thu, Dec 15, 2022 at 05:26:20PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> lld cannot build for ARMv4/v4T targets because it inserts 'blx' instructions
> that are unsupported there:
> 
>   ld.lld: warning: lld uses blx instruction, no object with architecture supporting feature detected
> 
> Add a Kconfig time dependency to prevent those targets from being
> selected in randconfig builds.
> 
> Link: https://github.com/llvm/llvm-project/issues/50764
> Link: https://github.com/ClangBuiltLinux/linux/issues/964
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Reviewed-by: Nathan Chancellor <nathan@kernel.org>

> ---
>  arch/arm/Kconfig | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index 4a8fff7f9be0..d995054ab602 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -344,12 +344,14 @@ comment "CPU Core family selection"
>  config ARCH_MULTI_V4
>  	bool "ARMv4 based platforms (FA526, StrongARM)"
>  	depends on !ARCH_MULTI_V6_V7
> +	depends on !LD_IS_LLD
>  	select ARCH_MULTI_V4_V5
>  	select CPU_FA526 if !(CPU_SA110 || CPU_SA1100)
>  
>  config ARCH_MULTI_V4T
>  	bool "ARMv4T based platforms (ARM720T, ARM920T, ...)"
>  	depends on !ARCH_MULTI_V6_V7
> +	depends on !LD_IS_LLD
>  	select ARCH_MULTI_V4_V5
>  	select CPU_ARM920T if !(CPU_ARM7TDMI || CPU_ARM720T || \
>  		CPU_ARM740T || CPU_ARM9TDMI || CPU_ARM922T || \
> -- 
> 2.35.1
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-12-16 23:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 16:26 [PATCH] ARM: disallow pre-ARMv5 builds with ld.lld Arnd Bergmann
2022-12-15 16:26 ` Arnd Bergmann
2022-12-16 23:10 ` Nathan Chancellor [this message]
2022-12-16 23:10   ` Nathan Chancellor
2022-12-19 16:00 ` patchwork-bot+linux-soc

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=Y5z66Oh1mcOul0Jw@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=llvm@lists.linux.dev \
    --cc=ndesaulniers@google.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=soc@kernel.org \
    --cc=trix@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.