From: Nathan Chancellor <nathan@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
llvm@lists.linux.dev, Nick Desaulniers <ndesaulniers@google.com>,
Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: arm64: clang-nightly: net/ipv4/tcp_input.c: clang: error: clang frontend command failed with exit code 139
Date: Mon, 14 Feb 2022 08:35:29 -0700 [thread overview]
Message-ID: <Ygp2wVo8JfWh5iOk@dev-arch.archlinux-ax161> (raw)
In-Reply-To: <CA+G9fYtR+E52X-ucmvXYG5-9v0q2UEXQsML=nkQRnSf7TwXYqw@mail.gmail.com>
Hi Naresh,
On Mon, Feb 14, 2022 at 12:27:17PM +0530, Naresh Kamboju wrote:
> On Linux mainline master branch with arm64 clang-nightly build failed
> due to following errors and warnings.
>
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/current LLVM=1 LLVM_IAS=1
> ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-
> CROSS_COMPILE_COMPAT=arm-linux-gnueabihf- HOSTCC=clang CC=clang
> PLEASE submit a bug report to
> https://github.com/llvm/llvm-project/issues/ and include the crash
> backtrace, preprocessed source, and associated run script.
> Stack dump:
<snip>
> 1. <eof> parser at end of file
> 2. Code generation
> 3. Running pass 'Function Pass Manager' on module
> '/builds/linux/net/ipv4/tcp_input.c'.
<snip>
> I have reported this a new issues on github,
> https://github.com/llvm/llvm-project/issues/53811
Thank you for the report! I found this over the weekend myself and
reverted the problematic commit in LLVM and I will make sure that if it
lands again, it can build a kernel without any issues.
https://github.com/llvm/llvm-project/commit/22eb1dae3fb20ca8ada865de1d95baab0e08a060
For the future, you may consider only sending reports of compiler
crashes to Nick, myself, and llvm@lists.linux.dev; a compiler crash is
pretty much never the fault of the source code so CC'ing Linux
maintainers is just noise.
Cheers,
Nathan
next prev parent reply other threads:[~2022-02-14 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 6:57 arm64: clang-nightly: net/ipv4/tcp_input.c: clang: error: clang frontend command failed with exit code 139 Naresh Kamboju
2022-02-14 15:35 ` Nathan Chancellor [this message]
2022-02-14 16:11 ` Naresh Kamboju
2022-02-15 19:10 ` Nick Desaulniers
2022-02-15 19:18 ` 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=Ygp2wVo8JfWh5iOk@dev-arch.archlinux-ax161 \
--to=nathan@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=ndesaulniers@google.com \
--cc=yoshfuji@linux-ipv6.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.