From: Nathan Chancellor <nathan@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-stable <stable@vger.kernel.org>,
llvm@lists.linux.dev,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shuah Khan <shuah@kernel.org>,
lkft-triage@lists.linaro.org
Subject: Re: Linux-stable-rc/ queue_5.10
Date: Mon, 19 Dec 2022 08:26:09 -0700 [thread overview]
Message-ID: <Y6CCkWLcNZMqN8UV@dev-arch.thelio-3990X> (raw)
In-Reply-To: <CA+G9fYs=G_AAbkNOfLv7Oyvt6uOZ8CYun8fUQ-GghoKtbD5WAw@mail.gmail.com>
Hi Naresh,
On Mon, Dec 19, 2022 at 08:47:32PM +0530, Naresh Kamboju wrote:
> The MIPS tinyconfig with clang nightly build failed,
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Build warnings / errors,
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/1/build LLVM=1 LLVM_IAS=0
> ARCH=mips CROSS_COMPILE=mips-linux-gnu- HOSTCC=clang CC=clang
> tinyconfig
>
> /tmp/calibrate-9ea8cf.s: Assembler messages:
> /tmp/calibrate-9ea8cf.s:134: Error: .module is not permitted after
> generating code
> /tmp/calibrate-9ea8cf.s:168: Error: .module is not permitted after
> generating code
> /tmp/calibrate-9ea8cf.s:192: Error: .module is not permitted after
> generating code
> /tmp/calibrate-9ea8cf.s:216: Error: .module is not permitted after
> generating code
> clang: error: assembler command failed with exit code 1 (use -v to see
> invocation)
> make[2]: *** [/builds/linux/scripts/Makefile.build:286:
> init/calibrate.o] Error 1
Thanks for the report. This is a toolchain regression that should
hopefully be resolved soon:
https://reviews.llvm.org/D138179#4002068
https://reviews.llvm.org/D140270
Cheers,
Nathan
prev parent reply other threads:[~2022-12-19 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 15:17 Linux-stable-rc/ queue_5.10 Naresh Kamboju
2022-12-19 15:26 ` Nathan Chancellor [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=Y6CCkWLcNZMqN8UV@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.