ARC: Get rid of toolchain check
Subsystems (2)
PATCH 1/1 ARC: Get rid of toolchain check
This check is very naive: we simply test if GCC invoked without "-mcpu=XXX" has ARC700 define set. In that case we think that GCC was built with "--with-cpu=arc700" and has libgcc built for ARC700.
Otherwise if ARC700 is not defined we think that everythng was built for ARCv2.
But in reality our life is much more interesting.
1. Regardless of GCC configuration (i.e. what we pass in "--with-cpu" it may generate code for any ARC core).
2. libgcc might be built with explicitly specified "--mcpu=YYY"
That's exactly what happens in case of multilibbed toolchains:
- GCC is configured with default settings
- All the libs built for many different CPU flavors
I.e. that check gets in the way of usage of multilibbed toolchains. And even non-multilibbed toolchains are affected. OpenEmbedded also builds GCC without "--with-cpu" because each and every target component later is compiled with explicitly set "-mcpu=ZZZ".
--- arch/arc/Makefile | 14 -------------- 1 file changed, 14 deletions(-)
arch/arc/Makefile +0 -14
@@ -20,20 +20,6 @@ cflags-y += -fno-common -pipe -fno-builtin -mmedium-calls -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
Signature · 1 line
2.17.1
Quoted 25 lines · Alexey Brodkin
This check is very naive: we simply test if GCC invoked without "-mcpu=XXX" has ARC700 define set. In that case we think that GCC was built with "--with-cpu=arc700" and has libgcc built for ARC700.
Otherwise if ARC700 is not defined we think that everythng was built for ARCv2.
But in reality our life is much more interesting.
1. Regardless of GCC configuration (i.e. what we pass in "--with-cpu" it may generate code for any ARC core).
2. libgcc might be built with explicitly specified "--mcpu=YYY"
That's exactly what happens in case of multilibbed toolchains:
- GCC is configured with default settings
- All the libs built for many different CPU flavorsI.e. that check gets in the way of usage of multilibbed toolchains. And even non-multilibbed toolchains are affected. OpenEmbedded also builds GCC without "--with-cpu" because each and every target component later is compiled with explicitly set "-mcpu=ZZZ".
Quoted 4 lines
Signed-off-by Alexey Brodkin <abrodkin at synopsys.com>--- arch/arc/Makefile | 14 -------------- 1 file changed, 14 deletions(-)
+1 for this. Removing it also helps with my work to be able to build all the .dts files with only a host compiler. That also needs the hunk setting CROSS_COMPILE removed and not having a built-in dtb by default, but this is a step in the right direction.
Rob
Hello,
Quoted 39 lines
-----Original Message-----
From: Rob Herring [mailto:robh at kernel.org]
Sent: Friday, September 14, 2018 12:04 AM
To: Alexey.Brodkin at synopsys.com
Cc: linux-snps-arc at lists.infradead.org; Linux Kernel Mailing List <linux-kernel at vger.kernel.org>; Vineet.Gupta1 at synopsys.com
Subject: Re: [PATCH] ARC: Get rid of toolchain checkQuoted 25 lines · Alexey Brodkin
This check is very naive: we simply test if GCC invoked without "-mcpu=XXX" has ARC700 define set. In that case we think that GCC was built with "--with-cpu=arc700" and has libgcc built for ARC700.
Otherwise if ARC700 is not defined we think that everythng was built for ARCv2.
But in reality our life is much more interesting.
1. Regardless of GCC configuration (i.e. what we pass in "--with-cpu" it may generate code for any ARC core).
2. libgcc might be built with explicitly specified "--mcpu=YYY"
That's exactly what happens in case of multilibbed toolchains:
- GCC is configured with default settings
- All the libs built for many different CPU flavorsI.e. that check gets in the way of usage of multilibbed toolchains. And even non-multilibbed toolchains are affected. OpenEmbedded also builds GCC without "--with-cpu" because each and every target component later is compiled with explicitly set "-mcpu=ZZZ".
Quoted 4 lines
Signed-off-by Alexey Brodkin <abrodkin at synopsys.com>--- arch/arc/Makefile | 14 -------------- 1 file changed, 14 deletions(-)
Quoted 6 lines
+1 for this. Removing it also helps with my work to be able to build all the .dts files with only a host compiler. That also needs the hunk setting
CROSS_COMPILEremoved and not having a built-in dtb by default, but this is a step in the right direction.Acked-by Rob Herring <robh at kernel.org>
May we get this one back-ported to stable trees?
Upstream commit in Linus' tree is615f64458ad8 ("ARC: build: Get rid of toolchain check").
This fixes kernel configuration for ARC in case of missing ARC cross-tools in current PATH.
-Alexey
[email protected]
maintainerQuoted 48 lines · Alexey Brodkin
Hello,
Quoted 39 lines
-----Original Message-----
From: Rob Herring [mailto:robh at kernel.org]
Sent: Friday, September 14, 2018 12:04 AM
To: Alexey.Brodkin at synopsys.com
Cc: linux-snps-arc at lists.infradead.org; Linux Kernel Mailing List <linux-kernel at vger.kernel.org>; Vineet.Gupta1 at synopsys.com
Subject: Re: [PATCH] ARC: Get rid of toolchain checkQuoted 25 lines · Alexey Brodkin
This check is very naive: we simply test if GCC invoked without "-mcpu=XXX" has ARC700 define set. In that case we think that GCC was built with "--with-cpu=arc700" and has libgcc built for ARC700.
Otherwise if ARC700 is not defined we think that everythng was built for ARCv2.
But in reality our life is much more interesting.
1. Regardless of GCC configuration (i.e. what we pass in "--with-cpu" it may generate code for any ARC core).
2. libgcc might be built with explicitly specified "--mcpu=YYY"
That's exactly what happens in case of multilibbed toolchains:
- GCC is configured with default settings
- All the libs built for many different CPU flavorsI.e. that check gets in the way of usage of multilibbed toolchains. And even non-multilibbed toolchains are affected. OpenEmbedded also builds GCC without "--with-cpu" because each and every target component later is compiled with explicitly set "-mcpu=ZZZ".
Quoted 4 lines
Signed-off-by Alexey Brodkin <abrodkin at synopsys.com>--- arch/arc/Makefile | 14 -------------- 1 file changed, 14 deletions(-)Quoted 6 lines
+1 for this. Removing it also helps with my work to be able to build all the .dts files with only a host compiler. That also needs the hunk setting
CROSS_COMPILEremoved and not having a built-in dtb by default, but this is a step in the right direction.Acked-by Rob Herring <robh at kernel.org>
Quoted 7 lines
May we get this one back-ported to stable trees?
Upstream commit in Linus' tree is
615f64458ad8("ARC: build: Get rid of toolchain check").This fixes kernel configuration for ARC in case of missing ARC cross-tools in current PATH.
Now queued up, thanks.
greg k-h