-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error monomorphizing rather complex use of ifaces #2283
Comments
Ugh. It turns out that the last snapshot, although registered after my fix, is actually a snapshot of a tree that's quite a bit older. I've verified that when I do a local snapshot, this problem goes away. So this is a duplicate of #2185, as Tim pointed out. I'll start a new snapshot. |
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Sep 22, 2022
revert --color=always changes They [cause problems](rust-lang/miri#2277) and they completely break rendering on the playground: ``` Compiling playground v0.0.1 (/playground) Finished dev [unoptimized + debuginfo] target(s) in 0.47s Running `/playground/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/cargo-miri target/miri/x86_64-unknown-linux-gnu/debug/playground` �[0m�[1m�[38;5;9merror[E0277]�[0m�[0m�[1m: `*mut std::sync::atomic::AtomicUsize` cannot be sent between threads safely�[0m �[0m �[0m�[0m�[1m�[38;5;12m--> �[0m�[0msrc/main.rs:17:18�[0m �[0m �[0m�[0m�[1m�[38;5;12m|�[0m �[0m�[1m�[38;5;12m17�[0m�[0m �[0m�[0m�[1m�[38;5;12m|�[0m�[0m �[0m�[0m let j1 = spawn(move || {�[0m �[0m �[0m�[0m�[1m�[38;5;12m| �[0m�[0m �[0m�[0m�[1m�[38;5;12m__________________�[0m�[0m�[1m�[38;5;9m^^^^^�[0m�[0m�[1m�[38;5;12m_-�[0m �[0m �[0m�[0m�[1m�[38;5;12m| �[0m�[0m�[1m�[38;5;12m|�[0m�[0m �[0m�[0m�[1m�[38;5;9m|�[0m �[0m �[0m�[0m�[1m�[38;5;12m| �[0m�[0m�[1m�[38;5;12m|�[0m�[0m �[0m�[0m�[1m�[38;5;9m`*mut std::sync::atomic::AtomicUsize` cannot be sent between threads safely�[0m �[0m�[1m�[38;5;12m18�[0m�[0m �[0m�[0m�[1m�[38;5;12m|�[0m�[0m �[0m�[0m�[1m�[38;5;12m|�[0m�[0m �[0m�[0m *(c.0 as *mut usize) = 32;�[0m �[0m�[1m�[38;5;12m19�[0m�[0m �[0m�[0m�[1m�[38;5;12m|�[0m�[0m �[0m�[0m�[1m�[38;5;12m|�[0m�[0m �[0m�[0m });�[0m �[0m �[0m�[0m�[1m�[38;5;12m| �[0m�[0m�[1m�[38;5;12m|_________-�[0m�[0m �[0m�[0m�[1m�[38;5;12mwithin this `[closure@src/main.rs:17:24: 19:10]`�[0m �[0m �[0m�[0m�[1m�[38;5;12m|�[0m ``` Sorry `@saethlin,` I think we need to go back to start here and consider another solution. Fixes rust-lang/miri#2277
jieyouxu
added a commit
to jieyouxu/rust
that referenced
this issue
Mar 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you look at the
iter
branch in thenikomatsakis/rust
repo, you will find that it fails in stage0. I debugged this a bit by building a vanilla compiler in another repoistory and managed to trace it as far as a failure inmake_mono_id()
because the call tomap2()
that is processing bounds and substs receives a bounds vec of length 1 and a substs vec of length 2. This seems to occur with the call tovec::flatmap()
that occurs in librustsyntax processing the attributes. I tried to narrow down the test to a smaller test file but was unable to find anything that reproduced the error other than the full rustc.@marijnh if you wouldn't mind taking a look and let me know if something jumps out at you, I would appreciate it.
The text was updated successfully, but these errors were encountered: