-
Notifications
You must be signed in to change notification settings - Fork 0
Open
model-checking/kani
#4312Description
error: `compiler_builtins` cannot call functions through upstream monomorphizations; encountered invalid call from `core::ops::index_range::IndexRange::next_unchecked` to `core::ops::index_range::IndexRange::next_unchecked::kani_contract_mode`
--> /home/runner/work/distributed-verification/distributed-verification/verify-rust-std/library/core/src/ops/index_range.rs:63:5
|
63 | #[cfg_attr(kani, kani::modifies(self))]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: this error originates in the attribute macro `kani::modifies` (in Nightly builds, run with -Z macro-backtrace for more info)
dv fails to compile compiler_builtins at 58b34c8
https://github.com/os-checker/distributed-verification/actions/runs/17088072312/job/48456215614
cc
-Zbuild-std
shouldn't explode on compiler-builtins fragility rust-lang/rust#137222- Is passing -Clink-dead-code by default still a good idea? rust-fuzz/cargo-fuzz#391
- https://github.com/model-checking/verify-rust-std/pull/451/files#diff-4560688b121853f7240d9741469cc46eafadc5d007b423e8a76e8f0d0de50f75 as the introduction of such annotations
kani::modifies
causes an error that compiler_builtins cannot call functions through upstream monomorphizations model-checking/verify-rust-std#477
But I've checked no -Clink-dead-code
is specified anywhere.
When the attribute is removed on IndexRange::next_unchecked
, all crates compile fine. 🤔
So not sure if this is a regression or something going wrong.
Metadata
Metadata
Assignees
Labels
No labels