From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: open list <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Linux Regressions <regressions@lists.linux.dev>,
lkft-triage@lists.linaro.org,
clang-built-linux <llvm@lists.linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
willy@infradead.org, David Hildenbrand <david@redhat.com>
Subject: next: x86_64 defconfig with clang-17 failed
Date: Thu, 28 Mar 2024 19:05:51 +0530 [thread overview]
Message-ID: <CA+G9fYvbFMMCmk91vzVXcS5T2Ezkwg8tQDgt_TfF-8Q=c0B0PQ@mail.gmail.com> (raw)
While building x86_64 defconfig with clang-17 the following build warnings /
errors noticed on Linux next-20240328 tag.
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Build error:
---------
mm/memory.c:5094:25: error: variable 'pte' is uninitialized when used
here [-Werror,-Wuninitialized]
5094 | writable = pte_write(pte);
| ^~~
mm/memory.c:5083:3: note: variable 'pte' is declared here
5083 | pte_t pte, old_pte;
| ^
1 error generated.
steps to reproduce:
----------
# tuxmake --runtime podman --target-arch x86_64 --toolchain clang-17
--kconfig x86_64_defconfig LLVM=1 LLVM_IAS=1
Links:
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240328/testrun/23230289/suite/build/test/clang-17-x86_64_defconfig/log
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240328/testrun/23230289/suite/build/test/clang-17-x86_64_defconfig/details/
- https://storage.tuxsuite.com/public/linaro/lkft/builds/2eIseG3mebbz7v0HESNW2YOTmiu/
--
Linaro LKFT
https://lkft.linaro.org
next reply other threads:[~2024-03-28 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 13:35 Naresh Kamboju [this message]
2024-03-28 18:50 ` Andrew Morton
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='CA+G9fYvbFMMCmk91vzVXcS5T2Ezkwg8tQDgt_TfF-8Q=c0B0PQ@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=regressions@lists.linux.dev \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox