From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh " <linux@weissschuh.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [thomas-weissschuh:b4/rust-dyndbg 11/15] error: `core::num::<impl u32>::bit_width` is not yet stable as a const fn
Date: Thu, 01 Oct 2026 08:06:50 +0200 [thread overview]
Message-ID: <202610010836.aVOF8yYD-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/rust-dyndbg
head: 8d3e0685c6f97f4b02dcb87274268a7ff4d7bd47
commit: 27766faadd51e77948e26881062ae8e4bc2c0f80 [11/15] rust: add support for dynamic debug
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20261001/202610010836.aVOF8yYD-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261001/202610010836.aVOF8yYD-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/202610010836.aVOF8yYD-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0658]: use of unstable library feature `uint_bit_width`
--> rust/kernel/dynamic_debug.rs:26:14
|
26 | if c.bit_width() > 8 {
| ^^^^^^^^^
|
= note: see issue #142326 <https://github.com/rust-lang/rust/issues/142326> for more information
= help: add `#![feature(uint_bit_width)]` to the crate attributes to enable
= note: this compiler was built on 2026-05-25; consider upgrading it if it is out of date
--
>> error: `core::num::<impl u32>::bit_width` is not yet stable as a const fn
--> rust/kernel/dynamic_debug.rs:26:12
|
26 | if c.bit_width() > 8 {
| ^^^^^^^^^^^^^
|
help: add `#![feature(uint_bit_width)]` to the crate attributes to enable
--> rust/kernel/lib.rs:38:1
|
38 + #![feature(uint_bit_width)]
|
--
>> error[E0658]: use of unstable library feature `uint_bit_width`
--> rust/kernel/dynamic_debug.rs:45:19
|
45 | if lineno.bit_width() > 18 || class_id.bit_width() > 6 {
| ^^^^^^^^^
|
= note: see issue #142326 <https://github.com/rust-lang/rust/issues/142326> for more information
= help: add `#![feature(uint_bit_width)]` to the crate attributes to enable
= note: this compiler was built on 2026-05-25; consider upgrading it if it is out of date
--
>> error[E0658]: use of unstable library feature `uint_bit_width`
--> rust/kernel/dynamic_debug.rs:45:48
|
45 | if lineno.bit_width() > 18 || class_id.bit_width() > 6 {
| ^^^^^^^^^
|
= note: see issue #142326 <https://github.com/rust-lang/rust/issues/142326> for more information
= help: add `#![feature(uint_bit_width)]` to the crate attributes to enable
= note: this compiler was built on 2026-05-25; consider upgrading it if it is out of date
--
>> error: `core::num::<impl u32>::bit_width` is not yet stable as a const fn
--> rust/kernel/dynamic_debug.rs:45:12
|
45 | if lineno.bit_width() > 18 || class_id.bit_width() > 6 {
| ^^^^^^^^^^^^^^^^^^
|
help: add `#![feature(uint_bit_width)]` to the crate attributes to enable
--> rust/kernel/lib.rs:38:1
|
38 + #![feature(uint_bit_width)]
|
--
>> error: `core::num::<impl u32>::bit_width` is not yet stable as a const fn
--> rust/kernel/dynamic_debug.rs:45:39
|
45 | if lineno.bit_width() > 18 || class_id.bit_width() > 6 {
| ^^^^^^^^^^^^^^^^^^^^
|
help: add `#![feature(uint_bit_width)]` to the crate attributes to enable
--> rust/kernel/lib.rs:38:1
|
38 + #![feature(uint_bit_width)]
|
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-01 6:07 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=202610010836.aVOF8yYD-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux@weissschuh.net \
--cc=llvm@lists.linux.dev \
--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.