From: kernel test robot <lkp@intel.com>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: <oe-kbuild-all@lists.linux.dev>,
<linux-m68k@lists.linux-m68k.org>, <uclinux-dev@uclinux.org>
Subject: [gerg-m68knommu:cf 1/11] lib/muldi3.c:53:28: sparse: sparse: asm output is not an lvalue
Date: Thu, 17 Oct 2024 09:13:44 +0800 [thread overview]
Message-ID: <ZxBkyGblxJ7jWzBI@rli9-mobl> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git cf
head: 472b9fae6baae3d777a1d49fa38893ad0e5f0d67
commit: 050dde147e3a6afee3df72e7252c9b59856cc2b9 [1/11] m68k: use kernel's generic muldi3 libgcc function
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: m68k-randconfig-r113-20241009 (https://download.01.org/0day-ci/archive/20241009/202410091720.grDsayDh-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.1.0
reproduce: (https://download.01.org/0day-ci/archive/20241009/202410091720.grDsayDh-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/r/202410091720.grDsayDh-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> lib/muldi3.c:53:28: sparse: sparse: asm output is not an lvalue
>> lib/muldi3.c:53:28: sparse: sparse: asm output is not an lvalue
>> lib/muldi3.c:53:28: sparse: sparse: not addressable
>> lib/muldi3.c:53:28: sparse: sparse: generating address of non-lvalue (11)
>> lib/muldi3.c:53:28: sparse: sparse: generating address of non-lvalue (11)
vim +53 lib/muldi3.c
b35cd9884fa5d8 Palmer Dabbelt 2017-05-23 48
b35cd9884fa5d8 Palmer Dabbelt 2017-05-23 49 long long notrace __muldi3(long long u, long long v)
b35cd9884fa5d8 Palmer Dabbelt 2017-05-23 50 {
b35cd9884fa5d8 Palmer Dabbelt 2017-05-23 51 const DWunion uu = {.ll = u};
b35cd9884fa5d8 Palmer Dabbelt 2017-05-23 52 const DWunion vv = {.ll = v};
b35cd9884fa5d8 Palmer Dabbelt 2017-05-23 @53 DWunion w = {.ll = __umulsidi3(uu.s.low, vv.s.low)};
:::::: The code at line 53 was first introduced by commit
:::::: b35cd9884fa5d81c9d5e7f57c9d03264ae2bd835 lib: Add shared copies of some GCC library routines
:::::: TO: Palmer Dabbelt <palmer@dabbelt.com>
:::::: CC: Palmer Dabbelt <palmer@dabbelt.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-10-17 1:13 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=ZxBkyGblxJ7jWzBI@rli9-mobl \
--to=lkp@intel.com \
--cc=gerg@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=uclinux-dev@uclinux.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