From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Yu-Chun Lin <eleanor15x@gmail.com>,
Tal Zussman <tz2294@columbia.edu>,
jserv@ccns.ncku.edu.tw
Subject: Re: [akpm-mm:mm-nonmm-unstable 32/32] ({ BUILDclang diag: _include/linux/compiler_attributes.h:138:56: warning: attribute 'error' is already applied with different arguments [-Wignored-attributes]B
Date: Tue, 10 Jun 2025 00:43:14 +0800 [thread overview]
Message-ID: <aEcPInFT31s1lCZP@visitorckw-System-Product-Name> (raw)
In-Reply-To: <202506090716.JryOipkx-lkp@intel.com>
On Mon, Jun 09, 2025 at 07:48:46AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
> head: 8172857ac52869c411762ce86802d127b0bb7546
> commit: 8172857ac52869c411762ce86802d127b0bb7546 [32/32] riscv: optimize gcd() performance on RISC-V without Zbb extension
> config: x86_64-buildonly-randconfig-001-20250609 (https://download.01.org/0day-ci/archive/20250609/202506090716.JryOipkx-lkp@intel.com/config)
> compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
> rustc: rustc 1.78.0 (9b00956e5 2024-04-29)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250609/202506090716.JryOipkx-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202506090716.JryOipkx-lkp@intel.com/
>
I wasn't able to reproduce the issue on the latest mm-nonmm-unstable
branch. However, after I manually applied the patch "[PATCH]
compiler_types: Remove unnecessary indirection in compiletime_assert()"
[1] on top of it, the issue appeared.
Since the patch pointed out by the test robot only touches RISC-V code,
and the issue shows up on x86, I believe it's reasonable to conclude
that the dropped compiler_types patch was the cause, rather than the
RISC-V gcd patch.
[1]: https://lore.kernel.org/lkml/20250607-compiletime_assert-v1-1-a8991a9be729@columbia.edu/
Regards,
Kuan-Wei
prev parent reply other threads:[~2025-06-09 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-08 23:48 kernel test robot
2025-06-09 16:43 ` Kuan-Wei Chiu [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=aEcPInFT31s1lCZP@visitorckw-System-Product-Name \
--to=visitorckw@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=eleanor15x@gmail.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tz2294@columbia.edu \
/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