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-kunit-assertion 15/15] error: literal out of range for `i32`
Date: Sun, 04 Oct 2026 12:06:55 +0800 [thread overview]
Message-ID: <202610041200.BnpXhO0V-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/rust-kunit-assertion
head: 694018da3a2ec9356bb827e371b124feaad71569
commit: 694018da3a2ec9356bb827e371b124feaad71569 [15/15] kunit: msg
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20261004/202610041200.BnpXhO0V-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261004/202610041200.BnpXhO0V-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/202610041200.BnpXhO0V-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error: literal out of range for `i32`
--> rust/kernel/drm/gem/shmem.rs:686:39
|
686 | assert_eq!(vmap.read32(0x20), 0xFEDCBA98);
| ^^^^^^^^^^
|
= note: the literal `0xFEDCBA98` (decimal `4275878552`) does not fit into the type `i32` and will become `-19088744i32`
= help: consider using the type `u32` instead
= note: `#[deny(overflowing_literals)]` on by default
help: to use as a negative number (decimal `-19088744`), consider using the type `u32` for the literal and cast it to `i32`
|
686 | assert_eq!(vmap.read32(0x20), 0xFEDCBA98u32 as i32);
| ++++++++++
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-04 4: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=202610041200.BnpXhO0V-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox