From: kernel test robot <lkp@intel.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: arch/xtensa/lib/umulsidi3.S:18:7: warning: "XCHAL_NO_MUL" is not defined, evaluates to 0
Date: Fri, 15 Sep 2023 05:14:37 +0800 [thread overview]
Message-ID: <202309150556.t0yCdv3g-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 9fdfb15a3dbf818e06be514f4abbfc071004cbe7
commit: 8939c58d68f97ce530f02d46c9f2b56c3ec88399 xtensa: add __umulsidi3 helper
date: 9 months ago
config: xtensa-randconfig-001-20230914 (https://download.01.org/0day-ci/archive/20230915/202309150556.t0yCdv3g-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230915/202309150556.t0yCdv3g-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/202309150556.t0yCdv3g-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/xtensa/lib/umulsidi3.S:18:7: warning: "XCHAL_NO_MUL" is not defined, evaluates to 0 [-Wundef]
18 | #elif XCHAL_NO_MUL
| ^~~~~~~~~~~~
arch/xtensa/lib/umulsidi3.S:159:5: warning: "XCHAL_NO_MUL" is not defined, evaluates to 0 [-Wundef]
159 | #if XCHAL_NO_MUL
| ^~~~~~~~~~~~
vim +/XCHAL_NO_MUL +18 arch/xtensa/lib/umulsidi3.S
11
12 #ifdef __XTENSA_CALL0_ABI__
13 abi_entry(32)
14 s32i a12, sp, 16
15 s32i a13, sp, 20
16 s32i a14, sp, 24
17 s32i a15, sp, 28
> 18 #elif XCHAL_NO_MUL
19 /* This is not really a leaf function; allocate enough stack space
20 to allow CALL12s to a helper function. */
21 abi_entry(32)
22 #else
23 abi_entry_default
24 #endif
25
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-14 21:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202309150556.t0yCdv3g-lkp@intel.com \
--to=lkp@intel.com \
--cc=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@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
all inboxes | Powered by JetHome®