Skip to content
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

Closed
nikomatsakis opened this issue Apr 25, 2012 · 2 comments
Closed

error monomorphizing rather complex use of ifaces #2283

nikomatsakis opened this issue Apr 25, 2012 · 2 comments

Comments

@nikomatsakis
Copy link
Contributor

If you look at the iter branch in the nikomatsakis/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 in make_mono_id() because the call to map2() 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 to vec::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.

@ghost ghost assigned marijnh Apr 25, 2012
@catamorphism
Copy link
Contributor

The symptoms look a lot like #2185 -- you have @marijnh 's fix for that, right?

@marijnh
Copy link
Contributor

marijnh commented Apr 25, 2012

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.

@marijnh marijnh closed this as completed Apr 25, 2012
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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants