linux-kernel - Re: [PATCH] arc: Remove sometimes misleading toolchain check

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: <09e88740-9aa5-0526-abc3-9374fc9af5e9@synopsys.com>
Date:   Wed, 7 Jun 2017 09:33:51 -0700
From:   Vineet Gupta <Vineet.Gupta1@...opsys.com>
To:     Alexey Brodkin <Alexey.Brodkin@...opsys.com>,
        <linux-snps-arc@...ts.infradead.org>
CC:     <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arc: Remove sometimes misleading toolchain check

On 05/25/2017 10:24 AM, Alexey Brodkin wrote:
> Thinking of a toolchains for ARCompact and ARCv2 ISAs we implicitly
> think about libgcc.a build for one of those ISAs which we're linking
> with. And given there's no multiarch uClibc toolchain for ARC
> (as probably for any other architecture) the assumption is the only way
> to get libgcc.a for desired ISA is from a toolchain built right for that
> same ISA.
> 
> So what we do we check what's GCC's default architecture ARC700 or not.
> But generally speaking default arch makes not a lot of sense if explicit
> command line option exist like "-mcpu=archs". In other words exactly the
> same GCC might build executables for both ARC700 and ARC HS38.
> 
> But in real life libgcc could be easily built on a separate step
> independently of the compiler and friends. And that really happens.
> 
> For example OpenEmbedded prefers to reuse the same toolchain for both
> arches having libgcc built separately.

So this is a goodness of OE. But unfortunately those of living with simpler build 
systems: Synopsys toolchain scripts or even Buildroot don't have this - right ?

So how will it help other developers avoid errors in the work flow when doing 
kernel builds for ARCompact and ARCv2.

The right solution is to kill off the libgcc dependency altogether form kernel. 
Just import math emulation code that we think is needed and build it in kernel !

> 
> Anyways given we have plans to get rid of libgcc dependency that change
> is sort of future proof.
> 
> Signed-off-by: Alexey Brodkin <abrodkin@...opsys.com>
> ---
>   arch/arc/Makefile | 14 --------------
>   1 file changed, 14 deletions(-)
> 
> diff --git a/arch/arc/Makefile b/arch/arc/Makefile
> index 44ef35d33956..d8c99fefaebb 100644
> --- a/arch/arc/Makefile
> +++ b/arch/arc/Makefile
> @@ -22,20 +22,6 @@ cflags-y	+= -fno-common -pipe -fno-builtin -D__linux__
>   cflags-$(CONFIG_ISA_ARCOMPACT)	+= -mA7
>   cflags-$(CONFIG_ISA_ARCV2)	+= -mcpu=archs
>   
> -is_700 = $(shell $(CC) -dM -E - < /dev/null | grep -q "ARC700" && echo 1 || echo 0)
> -
> -ifdef CONFIG_ISA_ARCOMPACT
> -ifeq ($(is_700), 0)
> -    $(error Toolchain not configured for ARCompact builds)
> -endif
> -endif
> -
> -ifdef CONFIG_ISA_ARCV2
> -ifeq ($(is_700), 1)
> -    $(error Toolchain not configured for ARCv2 builds)
> -endif
> -endif
> -
>   ifdef CONFIG_ARC_CURR_IN_REG
>   # For a global register defintion, make sure it gets passed to every file
>   # We had a customer reported bug where some code built in kernel was NOT using
>