thread 'rustc' panicked at compiler/rustc_middle/src/ty/predicate.rs:514:9

[hkBst]

Summary

Running:
$ x clippy -A warnings -A clippy::all -D clippy::correctness -W clippy::suspicious -W clippy::style -W clippy::pedantic

caused thread 'rustc' panicked at compiler/rustc_middle/src/ty/predicate.rs:514:9.

Version

rustc 1.91.0-nightly (af00ff2ce 2025-09-04)
binary: rustc
commit-hash: af00ff2ce62b6617ed19305ae39e135ac71d0b22
commit-date: 2025-09-04
host: aarch64-unknown-linux-gnu
release: 1.91.0-nightly
LLVM version: 21.1.0

Error output

Backtrace

Building bootstrap
  Finished `dev` profile [unoptimized] target(s) in 0.09s
/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/ci-llvm/bin/llvm-strip does not exist; skipping copy
Building stage1 compiler artifacts (stage0 -> stage1, aarch64-unknown-linux-gnu)
  Finished `release` profile [optimized + debuginfo] target(s) in 0.35s
Creating a sysroot for stage1 compiler (use `rustup toolchain link 'name' build/host/stage1`)
Building stage1 clippy-driver (stage0 -> stage1, aarch64-unknown-linux-gnu)
  Finished `release` profile [optimized + debuginfo] target(s) in 0.20s
Building stage1 cargo-clippy (stage0 -> stage1, aarch64-unknown-linux-gnu)
  Finished `release` profile [optimized + debuginfo] target(s) in 0.19s
Linting stage1 library{alloc, compiler_builtins, core, panic_abort, panic_unwind, proc_macro, rustc-std-workspace-core, std, std_detect, sysroot, test, unwind} (stage1 -> stage1, aarch64-unknown-linux-gnu)
  Finished `release` profile [optimized + debuginfo] target(s) in 0.04s
Linting stage1 compiler{rustc-main, rustc_abi, rustc_arena, rustc_ast, rustc_ast_ir, rustc_ast_lowering, rustc_ast_passes, rustc_ast_pretty, rustc_attr_parsing, rustc_baked_icu_data, rustc_borrowck, rustc_builtin_macros, rustc_codegen_llvm, rustc_codegen_ssa, rustc_const_eval, rustc_data_structures, rustc_driver, rustc_driver_impl, rustc_error_codes, rustc_error_messages, rustc_errors, rustc_expand, rustc_feature, rustc_fluent_macro, rustc_fs_util, rustc_graphviz, rustc_hashes, rustc_hir, rustc_hir_analysis, rustc_hir_id, rustc_hir_pretty, rustc_hir_typeck, rustc_incremental, rustc_index, rustc_index_macros, rustc_infer, rustc_interface, rustc_lexer, rustc_lint, rustc_lint_defs, rustc_llvm, rustc_log, rustc_macros, rustc_metadata, rustc_middle, rustc_mir_build, rustc_mir_dataflow, rustc_mir_transform, rustc_monomorphize, rustc_next_trait_solver, rustc_parse, rustc_parse_format, rustc_passes, rustc_pattern_analysis, rustc_privacy, rustc_proc_macro, rustc_public, rustc_public_bridge, rustc_query_impl, rustc_query_system, rustc_resolve, rustc_sanitizers, rustc_serialize, rustc_session, rustc_span, rustc_symbol_mangling, rustc_target, rustc_thread_pool, rustc_trait_selection, rustc_traits, rustc_transmute, rustc_ty_utils, rustc_type_ir, rustc_type_ir_macros} (stage0 -> stage1, aarch64-unknown-linux-gnu)
  Checking rustc_session v0.0.0 (/home/gh-hkBst/rust/compiler/rustc_session)

thread 'rustc' panicked at compiler/rustc_middle/src/ty/predicate.rs:514:9:
`<dyn config::dep_tracking::DepTrackingHash as std::marker::Sized>` has escaping bound vars, so it cannot be wrapped in a dummy binder.
stack backtrace:
 0: __rustc::rust_begin_unwind
           at /rustc/788da80fcfcef3f34c90def5baa32813e39a1a41/library/std/src/panicking.rs:697:5
 1: core::panicking::panic_fmt
           at /rustc/788da80fcfcef3f34c90def5baa32813e39a1a41/library/core/src/panicking.rs:75:14
 2: rustc_trait_selection::traits::type_known_to_meet_bound_modulo_regions
 3: rustc_ty_utils::common_traits::is_item_raw
    [... omitted 1 frame ...]
 4: rustc_ty_utils::layout::layout_of_uncached
 5: rustc_ty_utils::layout::layout_of
    [... omitted 1 frame ...]
 6: <clippy_lints::zero_sized_map_values::ZeroSizedMapValues as rustc_lint::passes::LateLintPass>::check_ty
 7: <rustc_lint::late::LateContextAndPass<rustc_lint::late::RuntimeCombinedLateLintPass> as rustc_hir::intravisit::Visitor>::visit_ty
 8: <rustc_lint::late::LateContextAndPass<rustc_lint::late::RuntimeCombinedLateLintPass> as rustc_hir::intravisit::Visitor>::visit_fn_decl
 9: <rustc_lint::late::LateContextAndPass<rustc_lint::late::RuntimeCombinedLateLintPass> as rustc_hir::intravisit::Visitor>::visit_fn
10: <rustc_lint::late::LateContextAndPass<rustc_lint::late::RuntimeCombinedLateLintPass> as rustc_hir::intravisit::Visitor>::visit_nested_item
11: <rustc_lint::late::LateContextAndPass<rustc_lint::late::RuntimeCombinedLateLintPass> as rustc_hir::intravisit::Visitor>::visit_nested_item
12: <rustc_lint::late::LateContextAndPass<rustc_lint::late::RuntimeCombinedLateLintPass> as rustc_hir::intravisit::Visitor>::visit_nested_item
13: rustc_lint::late::check_crate::{closure#0}
14: rustc_lint::late::check_crate
15: rustc_interface::passes::analysis
    [... omitted 1 frame ...]
16: rustc_interface::passes::create_and_enter_global_ctxt::<core::option::Option<rustc_interface::queries::Linker>, rustc_driver_impl::run_compiler::{closure#0}::{closure#2}>::{closure#2}::{closure#0}
17: rustc_interface::interface::run_compiler::<(), rustc_driver_impl::run_compiler::{closure#0}>::{closure#1}
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

error: the compiler unexpectedly panicked. this is a bug.

note: using internal features is not supported and expected to cause internal compiler errors when used incorrectly

note: please attach the file at `/home/gh-hkBst/rust/rustc-ice-2025-09-05T11_06_29-296818.txt` to your bug report

note: compiler flags: --crate-type lib -C opt-level=3 -C embed-bitcode=no -C debuginfo=line-tables-only -C debug-assertions=on -C overflow-checks=off -C incremental=[REDACTED] -C symbol-mangling-version=v0 -Z unstable-options -Z force-unstable-if-unmarked -Z macro-backtrace -C split-debuginfo=off -C force-frame-pointers=true -C llvm-args=-import-instr-limit=10 -C link-args=-Wl,-z,origin -C link-args=-Wl,-rpath,$ORIGIN/../lib -Z on-broken-pipe=kill -C lto=off -Z binary-dep-depinfo -Z tls-model=initial-exec -Z force-unstable-if-unmarked

note: some of the compiler flags provided by cargo are hidden

query stack during panic:
#0 [is_sized_raw] computing whether `dyn config::dep_tracking::DepTrackingHash` is `Sized`
#1 [layout_of] computing layout of `&dyn config::dep_tracking::DepTrackingHash`
#2 [analysis] running analysis passes on this crate
end of query stack
note: Clippy version: clippy 0.1.90 (788da80fcf 2025-08-04)

error: could not compile `rustc_session` (lib)

Caused by:
process didn't exit successfully: `/home/gh-hkBst/rust/build/bootstrap/debug/rustc /home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage0/bin/clippy-driver /home/gh-hkBst/rust/build/bootstrap/debug/rustc --crate-name rustc_session --edition=2024 compiler/rustc_session/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=211 --crate-type lib --emit=dep-info,metadata -C opt-level=3 -C embed-bitcode=no -C debuginfo=line-tables-only -C debug-assertions=on -C overflow-checks=off --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=a169beae41a440e0 -C extra-filename=-4df93cde2f31467b --out-dir /home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps --target aarch64-unknown-linux-gnu -C incremental=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/incremental -L dependency=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps -L dependency=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/release/deps --extern bitflags=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/libbitflags-f905ef7a2cddfe55.rmeta --extern getopts=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/libgetopts-ea759cc5227367c9.rmeta --extern libc=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/liblibc-5a9b0b2112d72139.rmeta --extern rand=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/librand-2b46aecf5d81a369.rmeta --extern rustc_abi=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_abi-db8aab5241f42b3e.rmeta --extern rustc_ast=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_ast-4491128283f7c71c.rmeta --extern rustc_data_structures=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_data_structures-4d704d591d660bfc.rmeta --extern rustc_errors=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_errors-cba7746cce9ff8be.rmeta --extern rustc_feature=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_feature-3805136cc50bcdf7.rmeta --extern rustc_fluent_macro=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/release/deps/librustc_fluent_macro-fdd4afa8f1333159.so --extern rustc_fs_util=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_fs_util-b869ed816bd9d0db.rmeta --extern rustc_hashes=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_hashes-9c423625ff636dd4.rmeta --extern rustc_hir=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_hir-62641ec7c9d1388f.rmeta --extern rustc_lint_defs=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_lint_defs-d9d2eaa38760341a.rmeta --extern rustc_macros=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/release/deps/librustc_macros-8195fe24fe8d7d34.so --extern rustc_serialize=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_serialize-45f7ca3fa9f08f8b.rmeta --extern rustc_span=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_span-49e95f5d27234112.rmeta --extern rustc_target=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_target-c5bb6cc5c350b406.rmeta --extern termize=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/libtermize-65ed6bd8cf7d5022.rmeta --extern tracing=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/deps/libtracing-655229a7313e3346.rmeta --cfg=bootstrap --sysroot /home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage0-sysroot --cfg=windows_raw_dylib -Csymbol-mangling-version=v0 -Zunstable-options '--check-cfg=cfg(bootstrap)' '--check-cfg=cfg(llvm_enzyme)' -Zforce-unstable-if-unmarked -Zmacro-backtrace -Csplit-debuginfo=off -Cforce-frame-pointers=true -Cllvm-args=-import-instr-limit=10 -Clink-args=-Wl,-z,origin '-Clink-args=-Wl,-rpath,$ORIGIN/../lib' -Alinker-messages -Zon-broken-pipe=kill -Clto=off -Z binary-dep-depinfo -L native=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/build/psm-bb071052b10841f8/out -L native=/home/gh-hkBst/rust/build/aarch64-unknown-linux-gnu/stage1-rustc/aarch64-unknown-linux-gnu/release/build/blake3-a21de03e09703979/out` (exit status: 101)
Build completed unsuccessfully in 0:00:07

[ada4a]

This is the same as #15429, which was fixed in #15434

@rustbot label S-fixed

I think 1.92.0-nightly will have the fix, so you can try updating

[hkBst]

Unfortunately even with the nightly compiler as default "x clippy" will use the stable one... :( so I'm not sure how to test this atm.

[samueltardieu]

The fix for #15434 is present in the compiler repository. Are you testing with an up-to-date repository?

[hkBst]

Yes, my repo is up-to-date:

commit bbcbc7818ba27c951f9fd881fd3ec4cd5123b741 (HEAD -> master, upstream/master)
Merge: caccb4d0368 6dafcaf6c85
Author: bors <bors@rust-lang.org>
Date:   Thu Sep 25 07:25:03 2025 +0000

[samueltardieu]

Confirmed being a different bug, I can reproduce it while the fix for #15429 is definitely in.

@rustbot label -S-fixed

[samueltardieu]

Looks like you're right when you're talking about running the stable Clippy. Although it generates the stage 1 clippy-driver and cargo-clippy, it looks like it's using stage0's Clippy mixed with invocations of stage 1's Clippy. I can' t make sense of this.

To test this, when I add a dbg!() in the code for the zero_sized_map_values lint and comment out the call to cx.layout_of(ty), I get some debug traces (which were just added), but I also get calls to the stage0 Clippy because the ICE still happens through layout_of() (which was just commented out). And the traces don't correspond to the problematic test, so a mix of both Clippy stages seems to be used.

I'll check with T-bootstrap. In the meantime, you should be able to run Clippy by adding --stage 2 but of course it takes much longer to compile.

[samueltardieu]

Opened a Zulip thread.