From: Nathan Chancellor <nathan@kernel.org>
To: ci_notify@linaro.org
Cc: Roman Lebedev <lebedev.ri@gmail.com>, llvm@lists.linux.dev
Subject: Re: [TCWG CI] Regression caused by llvm: [SCEV] Sequential/in-order `UMin` expression
Date: Tue, 11 Jan 2022 23:50:21 -0700 [thread overview]
Message-ID: <Yd56LdGd17JZe+br@archlinux-ax161> (raw)
In-Reply-To: <1113802202.11035.1641968209817@jenkins.jenkins>
On Wed, Jan 12, 2022 at 06:16:48AM +0000, ci_notify@linaro.org wrote:
> [TCWG CI] Regression caused by llvm: [SCEV] Sequential/in-order `UMin` expression:
> commit 82fb4f4b223d78e86647f3576e41e3086ab42cd5
> Author: Roman Lebedev <lebedev.ri@gmail.com>
>
> [SCEV] Sequential/in-order `UMin` expression
...
> # 00:05:01 clang-14: error: clang frontend command failed with exit code 134 (use -v to see invocation)
> # 00:05:01 make[3]: *** [scripts/Makefile.build:277: sound/core/oss/route.o] Error 134
> # 00:05:03 make[2]: *** [scripts/Makefile.build:540: sound/core/oss] Error 2
Reported yesterday:
https://reviews.llvm.org/D116766
Fixed this morning:
https://reviews.llvm.org/rG76a0abbc13cdfd3ae71f8db8a9376f65a9f6f725
Cheers,
Nathan
prev parent reply other threads:[~2022-01-12 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 6:16 [TCWG CI] Regression caused by llvm: [SCEV] Sequential/in-order `UMin` expression ci_notify
2022-01-12 6:50 ` 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=Yd56LdGd17JZe+br@archlinux-ax161 \
--to=nathan@kernel.org \
--cc=ci_notify@linaro.org \
--cc=lebedev.ri@gmail.com \
--cc=llvm@lists.linux.dev \
/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