From: Nathan Chancellor <nathan@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: clang-built-linux <llvm@lists.linux.dev>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
lkft-triage@lists.linaro.org,
Nick Desaulniers <ndesaulniers@google.com>,
Anders Roxell <anders.roxell@linaro.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: clang nightly builds failing on PowerPc
Date: Fri, 19 Sep 2025 15:28:04 -0700 [thread overview]
Message-ID: <20250919222804.GA44805@ax162> (raw)
In-Reply-To: <aM071XHb5cppdEKK@stanley.mountain>
Hi Dan,
On Fri, Sep 19, 2025 at 02:17:41PM +0300, Dan Carpenter wrote:
> Hi the Clang nightly builds are failing on PowerPC with the
> ppc64e_defconfig. They started failing on Sept 11. Clang is failing on
> PowerPC in both linux-next and stable so it seems like something changed
> in Clang and not the kernel.
>
> Unfortunately I don't have ready access to the /tmp/vgetrandom-fef220.c
> file that was generated, but hopefully these logs are enough to reproduce
> the issue.
Indeed, thanks a lot for the report. I was able to reproduce this
locally, bisect LLVM to find the problematic commit, and report it
upstream:
https://github.com/llvm/llvm-project/pull/157206#issuecomment-3313700961
Hopefully it can be resolved quickly.
Cheers,
Nathan
prev parent reply other threads:[~2025-09-19 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+G9fYsJq0sPC+q6vLNKUgBqCGmmjDrfeP4R1-95Eu28FJRY_A@mail.gmail.com>
[not found] ` <20230612185424.GA2891387@dev-arch.thelio-3990X>
[not found] ` <CA+G9fYtX6YNqmz9vxJxa5cA5Uf2rr=RNM0nkoTzRpg79Azp2tA@mail.gmail.com>
[not found] ` <CA+G9fYvmqz3nQ=Cgs=7J6vtRj=OhbNzgkLPmxxN+vOBTU=9zVA@mail.gmail.com>
2025-09-19 11:17 ` clang nightly builds failing on PowerPc Dan Carpenter
2025-09-19 22:28 ` 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=20250919222804.GA44805@ax162 \
--to=nathan@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).