From: kernel test robot <lkp@intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [linux-next:master 11711/11779] include/asm-generic/bitops/generic-non-atomic.h:128: undefined reference to `__udivdi3'
Date: Sat, 17 May 2025 04:22:05 +0800 [thread overview]
Message-ID: <202505170435.9PHcbsp6-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 8566fc3b96539e3235909d6bdda198e1282beaed
commit: 233e9b69967c707b3b7573752bf6cd6707972684 [11711/11779] Merge branch 'timers/drivers/next' of https://git.linaro.org/people/daniel.lezcano/linux.git
config: xtensa-randconfig-001-20250516 (https://download.01.org/0day-ci/archive/20250517/202505170435.9PHcbsp6-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250517/202505170435.9PHcbsp6-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/202505170435.9PHcbsp6-lkp@intel.com/
All errors (new ones prefixed by >>):
xtensa-linux-ld: drivers/clocksource/timer-tegra186.o: in function `tegra186_timer_remove':
drivers/clocksource/timer-tegra186.c:479: undefined reference to `__udivdi3'
xtensa-linux-ld: drivers/clocksource/timer-tegra186.o: in function `generic_test_bit':
>> include/asm-generic/bitops/generic-non-atomic.h:128: undefined reference to `__udivdi3'
vim +128 include/asm-generic/bitops/generic-non-atomic.h
21bb8af513d35c Alexander Lobakin 2022-06-24 114
21bb8af513d35c Alexander Lobakin 2022-06-24 115 /**
21bb8af513d35c Alexander Lobakin 2022-06-24 116 * generic_test_bit - Determine whether a bit is set
21bb8af513d35c Alexander Lobakin 2022-06-24 117 * @nr: bit number to test
21bb8af513d35c Alexander Lobakin 2022-06-24 118 * @addr: Address to start counting from
21bb8af513d35c Alexander Lobakin 2022-06-24 119 */
0e862838f29014 Alexander Lobakin 2022-06-24 120 static __always_inline bool
0e862838f29014 Alexander Lobakin 2022-06-24 121 generic_test_bit(unsigned long nr, const volatile unsigned long *addr)
21bb8af513d35c Alexander Lobakin 2022-06-24 122 {
21bb8af513d35c Alexander Lobakin 2022-06-24 123 /*
21bb8af513d35c Alexander Lobakin 2022-06-24 124 * Unlike the bitops with the '__' prefix above, this one *is* atomic,
21bb8af513d35c Alexander Lobakin 2022-06-24 125 * so `volatile` must always stay here with no cast-aways. See
21bb8af513d35c Alexander Lobakin 2022-06-24 126 * `Documentation/atomic_bitops.txt` for the details.
21bb8af513d35c Alexander Lobakin 2022-06-24 127 */
21bb8af513d35c Alexander Lobakin 2022-06-24 @128 return 1UL & (addr[BIT_WORD(nr)] >> (nr & (BITS_PER_LONG-1)));
21bb8af513d35c Alexander Lobakin 2022-06-24 129 }
21bb8af513d35c Alexander Lobakin 2022-06-24 130
:::::: The code at line 128 was first introduced by commit
:::::: 21bb8af513d35c005c401706030f4eb469538d1d bitops: always define asm-generic non-atomic bitops
:::::: TO: Alexander Lobakin <alexandr.lobakin@intel.com>
:::::: CC: Yury Norov <yury.norov@gmail.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-16 20:22 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=202505170435.9PHcbsp6-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel.lezcano@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.