From: kernel test robot <lkp@intel.com>
To: Charlie Jenkins <charlie@rivosinc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Ard Biesheuvel <ardb@kernel.org>,
Ben Dooks <ben.dooks@codethink.co.uk>,
Pasha Bouzarjomehri <pasha@rivosinc.com>,
Emil Renner Berthing <emil.renner.berthing@canonical.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org,
Charlie Jenkins <charlie@rivosinc.com>
Subject: Re: [PATCH v4] riscv: Add runtime constant support
Date: Tue, 4 Feb 2025 01:06:51 +0800 [thread overview]
Message-ID: <202502040018.8DyjnzNe-lkp@intel.com> (raw)
In-Reply-To: <20250130-runtime_const_riscv-v4-1-2d36c41b7b9c@rivosinc.com>
Hi Charlie,
kernel test robot noticed the following build errors:
[auto build test ERROR on ffd294d346d185b70e28b1a28abe367bbfe53c04]
url: https://github.com/intel-lab-lkp/linux/commits/Charlie-Jenkins/riscv-Add-runtime-constant-support/20250131-092950
base: ffd294d346d185b70e28b1a28abe367bbfe53c04
patch link: https://lore.kernel.org/r/20250130-runtime_const_riscv-v4-1-2d36c41b7b9c%40rivosinc.com
patch subject: [PATCH v4] riscv: Add runtime constant support
config: riscv-randconfig-002-20250203 (https://download.01.org/0day-ci/archive/20250204/202502040018.8DyjnzNe-lkp@intel.com/config)
compiler: riscv32-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250204/202502040018.8DyjnzNe-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/202502040018.8DyjnzNe-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from fs/dcache.c:38:
arch/riscv/include/asm/runtime-const.h: In function '__runtime_fixup_ptr':
arch/riscv/include/asm/runtime-const.h:167:63: warning: right shift count >= width of type [-Wshift-count-overflow]
167 | __runtime_fixup_32(where + 4, where + 12, val >> 32);
| ^~
fs/dcache.c: In function 'd_hash':
arch/riscv/include/asm/runtime-const.h:13:28: warning: unused variable '__tmp' [-Wunused-variable]
13 | typeof(sym) __ret, __tmp; \
| ^~~~~
fs/dcache.c:112:16: note: in expansion of macro 'runtime_const_ptr'
112 | return runtime_const_ptr(dentry_hashtable) +
| ^~~~~~~~~~~~~~~~~
fs/dcache.c: Assembler messages:
>> fs/dcache.c:116: Error: illegal operands `addi a0,-0x211'
vim +116 fs/dcache.c
ceb5bdc2d246f6 Nicholas Piggin 2011-01-07 115
94bdd655caba20 Al Viro 2016-04-15 @116 #define IN_LOOKUP_SHIFT 10
94bdd655caba20 Al Viro 2016-04-15 117 static struct hlist_bl_head in_lookup_hashtable[1 << IN_LOOKUP_SHIFT];
94bdd655caba20 Al Viro 2016-04-15 118
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-02-03 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 1:26 [PATCH v4] riscv: Add runtime constant support Charlie Jenkins
2025-02-03 17:06 ` kernel test robot [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=202502040018.8DyjnzNe-lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@kernel.org \
--cc=ben.dooks@codethink.co.uk \
--cc=charlie@rivosinc.com \
--cc=emil.renner.berthing@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=pasha@rivosinc.com \
--cc=paul.walmsley@sifive.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