From: kernel test robot <lkp@intel.com>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: arch/arc/include/asm/io.h:139: Error: inappropriate arguments for opcode 'stw'
Date: Mon, 14 Jul 2025 22:52:19 +0800 [thread overview]
Message-ID: <202507142219.ROyOoLsc-lkp@intel.com> (raw)
Hi Serge,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 347e9f5043c89695b01e66b3ed111755afcf1911
commit: f6bb3e9d98c2e8d70587d5ddaf9426ef30d7865c net: pcs: xpcs: Add Synopsys DW xPCS platform device driver
date: 1 year ago
config: arc-axs103_smp_defconfig (https://download.01.org/0day-ci/archive/20250714/202507142219.ROyOoLsc-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250714/202507142219.ROyOoLsc-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/202507142219.ROyOoLsc-lkp@intel.com/
All errors (new ones prefixed by >>):
arch/arc/include/asm/io.h: Assembler messages:
>> arch/arc/include/asm/io.h:139: Error: inappropriate arguments for opcode 'stw'
>> arch/arc/include/asm/io.h:139: Error: inappropriate arguments for opcode 'stw'
>> arch/arc/include/asm/io.h:139: Error: inappropriate arguments for opcode 'stw'
vim +/stw +139 arch/arc/include/asm/io.h
1162b0701b14ba Vineet Gupta 2013-01-18 135
1162b0701b14ba Vineet Gupta 2013-01-18 136 #define __raw_writew __raw_writew
1162b0701b14ba Vineet Gupta 2013-01-18 137 static inline void __raw_writew(u16 s, volatile void __iomem *addr)
1162b0701b14ba Vineet Gupta 2013-01-18 138 {
1162b0701b14ba Vineet Gupta 2013-01-18 @139 __asm__ __volatile__(
1162b0701b14ba Vineet Gupta 2013-01-18 140 " stw%U1 %0, %1 \n"
1162b0701b14ba Vineet Gupta 2013-01-18 141 :
1162b0701b14ba Vineet Gupta 2013-01-18 142 : "r" (s), "m" (*(volatile u16 __force *)addr)
1162b0701b14ba Vineet Gupta 2013-01-18 143 : "memory");
1162b0701b14ba Vineet Gupta 2013-01-18 144
:::::: The code at line 139 was first introduced by commit
:::::: 1162b0701b14ba112d4e3fe5c27c694caf983539 ARC: I/O and DMA Mappings
:::::: TO: Vineet Gupta <vgupta@synopsys.com>
:::::: CC: Vineet Gupta <vgupta@synopsys.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-07-14 14:53 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=202507142219.ROyOoLsc-lkp@intel.com \
--to=lkp@intel.com \
--cc=fancer.lancer@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®