From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Vladimir Murzin <vladimir.murzin@arm.com>,
Kees Cook <keescook@chromium.org>,
Linus Walleij <linus.walleij@linaro.org>,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: arm: tinyconfig: entry-common.S:156: Error: r13 not allowed here -- `bic tsk,sp,#(((1<<12)<<1)-1)&~63'
Date: Tue, 21 Jul 2020 16:46:36 +0100 [thread overview]
Message-ID: <20200721154635.GA1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAK8P3a1DYvyzkFQDPPnK1p4yUZ-Zp+Pg2Lg9QKO_wnjbnHygnw@mail.gmail.com>
On Tue, Jul 21, 2020 at 05:43:15PM +0200, Arnd Bergmann wrote:
> On Tue, Jul 21, 2020 at 5:07 PM Naresh Kamboju
> <naresh.kamboju@linaro.org> wrote:
> >
> > This might add little value.
> >
> > arm build sets failed on linux next 20200721.
> > The defconfig ( +config fragments ) builds PASS.
> > The tinyconfig and allnoconfig FAILED with gcc-8, gcc-9 and gcc-10.
> >
> > make -sk KBUILD_BUILD_USER=TuxBuild -C/linux -j32 ARCH=arm
> > CROSS_COMPILE=arm-linux-gnueabihf- HOSTCC=gcc CC="sccache
> > arm-linux-gnueabihf-gcc" O=build zImage
> > #
> > ../arch/arm/kernel/entry-common.S: Assembler messages:
> > ../arch/arm/kernel/entry-common.S:156: Error: r13 not allowed here --
> > `bic tsk,sp,#(((1<<12)<<1)-1)&~63'
> > ../arch/arm/kernel/entry-common.S:243: Error: r13 not allowed here --
> > `bic tsk,sp,#(((1<<12)<<1)-1)&~63'
> > make[3]: *** [../scripts/Makefile.build:361:
> > arch/arm/kernel/entry-common.o] Error 1
> > ../arch/arm/kernel/entry-v7m.S: Assembler messages:
> > ../arch/arm/kernel/entry-v7m.S:60: Error: r13 not allowed here -- `bic
> > tsk,sp,#(((1<<12)<<1)-1)&~63'
> > ../arch/arm/kernel/entry-v7m.S:86: Error: r13 not allowed here -- `bic
> > tsk,sp,#(((1<<12)<<1)-1)&~63'
> > make[3]: *** [../scripts/Makefile.build:361:
> > arch/arm/kernel/entry-v7m.o] Error 1
> >
> > full build link,
> > https://gitlab.com/Linaro/lkft/kernel-runs/-/jobs/648560264
>
> This must come from
> ac5bb8f8445f ("ARM: 8983/1: asm: Rewrite get_thread_info using BIC")
>
> Adding Linus and Ard to Cc as well.
Absolutely no point.
It was known about last night (see your irc scrollback - I mentioned it
to sfr). It was reported earlier this afternoon just after I dropped
the commit. It's now been reported again.
So, please ignore these reports.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
prev parent reply other threads:[~2020-07-21 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 15:06 arm: tinyconfig: entry-common.S:156: Error: r13 not allowed here -- `bic tsk,sp,#(((1<<12)<<1)-1)&~63' Naresh Kamboju
2020-07-21 15:43 ` Arnd Bergmann
2020-07-21 15:46 ` Russell King - ARM Linux admin [this message]
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=20200721154635.GA1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=keescook@chromium.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=vladimir.murzin@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).