From: Nathan Chancellor <nathan@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: llvm@lists.linux.dev, lkft-triage@lists.linaro.org,
Nick Desaulniers <ndesaulniers@google.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: [next] mips: clang-14-defconfig build regression
Date: Thu, 3 Mar 2022 10:05:22 -0700 [thread overview]
Message-ID: <YiD1UruDryIyZAJc@dev-arch.thelio-3990X> (raw)
In-Reply-To: <CA+G9fYs3GavpYh6V_yTUGNbAU70mygVxBKvqoq=xh20pw1Wvow@mail.gmail.com>
Hi Naresh,
On Thu, Mar 03, 2022 at 09:09:56AM +0530, Naresh Kamboju wrote:
> [Please ignore this email if it is already reported]
>
> Linux next-20220302 mips builds failed [1] & [2].
>
> Regressions found on mips:
>
> - mips-clang-12-defconfig
> - mips-clang-13-allnoconfig
> - mips-clang-12-allnoconfig
> - mips-clang-12-tinyconfig
> - mips-clang-13-defconfig
> - mips-clang-11-tinyconfig
> - mips-clang-11-defconfig
> - mips-clang-nightly-allnoconfig
> - mips-clang-14-tinyconfig
> - mips-clang-14-defconfig
> - mips-clang-11-allnoconfig
> - mips-clang-nightly-tinyconfig
> - mips-clang-13-tinyconfig
> - mips-clang-nightly-defconfig
> - mips-clang-14-allnoconfig
>
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/1/build LLVM=1 LLVM_IAS=1
> ARCH=mips CROSS_COMPILE=mips-linux-gnu- 'HOSTCC=sccache clang'
> 'CC=sccache clang' defconfig
<snip>
> fatal error: error in backend: Invalid register name global variable
Thanks a lot for the report! Our CI caught this as well, I have filed an
issue on our tracker and the upstream LLVM one:
https://github.com/ClangBuiltLinux/linux/issues/1608
https://github.com/llvm/llvm-project/issues/54174
CC Kees, just as an FYI because of commit 200ed341b864 ("mips: Implement
"current_stack_pointer"").
Cheers,
Nathan
next prev parent reply other threads:[~2022-03-03 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 3:39 [next] mips: clang-14-defconfig build regression Naresh Kamboju
2022-03-03 17:05 ` Nathan Chancellor [this message]
2022-03-03 17:36 ` Kees Cook
2022-03-03 19:37 ` Nick Desaulniers
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=YiD1UruDryIyZAJc@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=keescook@chromium.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=ndesaulniers@google.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