From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"lkft-triage@lists.linaro.org" <lkft-triage@lists.linaro.org>
Cc: Jens Axboe <axboe@kernel.dk>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Christian Brauner <christian@brauner.io>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: arc: kernel/entry.S:310: Error: inappropriate arguments for opcode 'and'
Date: Fri, 30 Oct 2020 18:53:21 +0000 [thread overview]
Message-ID: <5273a136-ac9c-94fc-b6e1-d7a0abf2b385@synopsys.com> (raw)
In-Reply-To: <CA+G9fYth+F1TnG6GQNKtrxvChvX9m+nGa8LKFG18WCzsqNJg5w@mail.gmail.com>
Hi Naresh,
On 10/30/20 3:29 AM, Naresh Kamboju wrote:
> arc defconfig build failed on linux next 20201030 with gcc-8 and gcc-9.
>
> make -sk KBUILD_BUILD_USER=TuxBuild -C/linux -j16 ARCH=arc
> CROSS_COMPILE=arc-elf32- HOSTCC=gcc CC="sccache arc-elf32-gcc" O=build
> uImage
> #
> ../arch/arc/kernel/entry.S: Assembler messages:
> ../arch/arc/kernel/entry.S:310: Error: inappropriate arguments for opcode 'and'
> make[3]: *** [../scripts/Makefile.build:364:
> arch/arc/kernel/entry-arcv2.o] Error 1
>
> Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
Thx for reporting this. This is due to the series Add support for
TIF_NOTIFY_SIGNAL
<https://lore.kernel.org/io-uring/20201026203230.386348-1-axboe@kernel.dk/#r>where
ARC patch is broken and I just replied to Jens about it. He will
hopefully fix it and push updated series to -next
Thx,
-Vineet
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next prev parent reply other threads:[~2020-10-30 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 10:29 arc: kernel/entry.S:310: Error: inappropriate arguments for opcode 'and' Naresh Kamboju
2020-10-30 18:53 ` Vineet Gupta [this message]
2020-10-30 18:54 ` Jens Axboe
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=5273a136-ac9c-94fc-b6e1-d7a0abf2b385@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=axboe@kernel.dk \
--cc=bigeasy@linutronix.de \
--cc=christian@brauner.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mingo@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=tglx@linutronix.de \
/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).