[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMj1kXGXNxXGiC4dmNXHkZ6n=J0Fhim3oSwNx4Bz5m9fEphJvQ@mail.gmail.com>
Date: Fri, 10 Apr 2020 13:15:08 +0200
From: Ard Biesheuvel <ardb@...nel.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: Jian Cai <caij2003@...il.com>,
Linus Walleij <linus.walleij@...aro.org>,
Peter Smith <Peter.Smith@....com>,
Stefan Agner <stefan@...er.ch>,
David Howells <dhowells@...hat.com>,
Mauro Carvalho Chehab <mchehab+samsung@...nel.org>,
Manoj Gupta <manojgupta@...gle.com>,
Benjamin Gaignard <benjamin.gaignard@...aro.org>,
"Joel Fernandes (Google)" <joel@...lfernandes.org>,
clang-built-linux <clang-built-linux@...glegroups.com>,
Ilie Halip <ilie.halip@...il.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Russell King <linux@...linux.org.uk>,
Krzysztof Kozlowski <krzk@...nel.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Sami Tolvanen <samitolvanen@...gle.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"Steven Rostedt (VMware)" <rostedt@...dmis.org>,
jiancai@...gle.com, Doug Anderson <armlinux@...isordat.com>,
Dan Williams <dan.j.williams@...el.com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Patrick Bellasi <patrick.bellasi@....com>,
Masami Hiramatsu <mhiramat@...nel.org>,
Tejun Heo <tj@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] ARM: do not assemble iwmmxt.S with LLVM toolchain
On Fri, 10 Apr 2020 at 11:56, Arnd Bergmann <arnd@...db.de> wrote:
>
> On Fri, Apr 10, 2020 at 1:28 AM Jian Cai <caij2003@...il.com> wrote:
> >
> > iwmmxt.S contains XScale instructions LLVM ARM backend does not support.
> > Skip this file if LLVM integrated assemmbler or LLD is used to build ARM
> > kernel.
> >
> > Signed-off-by: Jian Cai <caij2003@...il.com>
>
> It clearly makes sense to limit the Kconfig option to compilers that
> can actually build it.
> A few questions though:
>
> - Given that Armada XP with its PJ4B was still marketed until fairly
> recently[1],
> wouldn't it make sense to still add support for it? Is it a lot of work?
>
The part of that file that the assembler chokes on hasn't been touched
by anyone since Nico added it 15+ years ago. It can only be built in
ARM mode, and it disassembles to the sequence below (the ld/st fe/fp
mnemonics are not document in recent versions of the ARM ARM, and
aren't understood by Clang either)
Instead of playing all these tricks with Kconfig, couldn't we simply
insert the bare opcodes and be done with it?
00000054 <concan_dump>:
54: fd812120 stc2 1, cr2, [r1, #128] ; 0x80
58: fd813121 stc2 1, cr3, [r1, #132] ; 0x84
5c: fd818122 stc2 1, cr8, [r1, #136] ; 0x88
60: fd819123 stc2 1, cr9, [r1, #140] ; 0x8c
64: fd81a124 stc2 1, cr10, [r1, #144] ; 0x90
68: fd81b125 stc2 1, cr11, [r1, #148] ; 0x94
6c: e3120002 tst r2, #2
70: 0a00000f beq b4 <concan_dump+0x60>
74: edc10100 stfe f0, [r1]
78: edc11102 stfe f1, [r1, #8]
7c: edc12104 stfe f2, [r1, #16]
80: edc13106 stfe f3, [r1, #24]
84: edc14108 stfe f4, [r1, #32]
88: edc1510a stfe f5, [r1, #40] ; 0x28
8c: edc1610c stfe f6, [r1, #48] ; 0x30
90: edc1710e stfe f7, [r1, #56] ; 0x38
94: edc18110 stfp f0, [r1, #64] ; 0x40
98: edc19112 stfp f1, [r1, #72] ; 0x48
9c: edc1a114 stfp f2, [r1, #80] ; 0x50
a0: edc1b116 stfp f3, [r1, #88] ; 0x58
a4: edc1c118 stfp f4, [r1, #96] ; 0x60
a8: edc1d11a stfp f5, [r1, #104] ; 0x68
ac: edc1e11c stfp f6, [r1, #112] ; 0x70
b0: edc1f11e stfp f7, [r1, #120] ; 0x78
b4: e3300000 teq r0, #0
b8: 012fff1e bxeq lr
000000bc <concan_load>:
bc: edd00100 ldfe f0, [r0]
c0: edd01102 ldfe f1, [r0, #8]
c4: edd02104 ldfe f2, [r0, #16]
c8: edd03106 ldfe f3, [r0, #24]
cc: edd04108 ldfe f4, [r0, #32]
d0: edd0510a ldfe f5, [r0, #40] ; 0x28
d4: edd0610c ldfe f6, [r0, #48] ; 0x30
d8: edd0710e ldfe f7, [r0, #56] ; 0x38
dc: edd08110 ldfp f0, [r0, #64] ; 0x40
e0: edd09112 ldfp f1, [r0, #72] ; 0x48
e4: edd0a114 ldfp f2, [r0, #80] ; 0x50
e8: edd0b116 ldfp f3, [r0, #88] ; 0x58
ec: edd0c118 ldfp f4, [r0, #96] ; 0x60
f0: edd0d11a ldfp f5, [r0, #104] ; 0x68
f4: edd0e11c ldfp f6, [r0, #112] ; 0x70
f8: edd0f11e ldfp f7, [r0, #120] ; 0x78
fc: fd902120 ldc2 1, cr2, [r0, #128] ; 0x80
100: fd903121 ldc2 1, cr3, [r0, #132] ; 0x84
104: fd908122 ldc2 1, cr8, [r0, #136] ; 0x88
108: fd909123 ldc2 1, cr9, [r0, #140] ; 0x8c
10c: fd90a124 ldc2 1, cr10, [r0, #144] ; 0x90
110: fd90b125 ldc2 1, cr11, [r0, #148] ; 0x94
114: e3310000 teq r1, #0
118: e3a02000 mov r2, #0
11c: 012fff1e bxeq lr
120: ee012110 flts f1, r2
124: e12fff1e bx lr
> - Why does the linker have to understand it, rather than just the assembler?
>
> > diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> > index 66a04f6f4775..39de8fc64a73 100644
> > --- a/arch/arm/Kconfig
> > +++ b/arch/arm/Kconfig
> > @@ -804,7 +804,7 @@ source "arch/arm/mm/Kconfig"
> >
> > config IWMMXT
> > bool "Enable iWMMXt support"
> > - depends on CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_PJ4 || CPU_PJ4B
> > + depends on !AS_IS_CLANG && !LD_IS_LLD && (CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_PJ4 || CPU_PJ4B)
>
> I would suggest splitting it into two lines for readability:
>
> depends on CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_PJ4 || CPU_PJ4B
> depends on !AS_IS_CLANG && !LD_IS_LLD
>
> Arnd
>
> [1] http://web.archive.org/web/20191015165247/https://www.marvell.com/embedded-processors/armada/index.jsp
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Powered by blists - more mailing lists