-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
"Cannot create local mono-item" ICE building cortex-m code on nightly #58323
Comments
Appears to work on stable and beta (with |
Triage, P-high for initial investigation; assigning latter to @michaelwoerister |
@jonas-schievink Do you know if this reproduces for other targets too? |
The obvious first step would be to reduce the test case down to something smaller. Even if it is not minimised, though, |
If this is a recent regression, it may be caused by the privacy/reachability changes (#56878) - some thing that's actually reachable is not marked as reachable, so we get the "mono-item" ICE. |
(If someone confirms that it's indeed a privacy issue and minimize, I'll fix it before the next release.) |
@michaelwoerister I'm not sure, I haven't yet investigated this at all |
@petrochenkov Yes, changes to reachability could easily cause something like this. |
https://github.com/rust-lang-nursery/cargo-bisect-rustc should be up to the task here. |
Thanks for bisecting, @jonas-schievink! This might have to do with @nagisa's implementation of |
This is the function for which the collector cannot find the MIR: It looks like the MIR for function is not encoded in metadata for some reason? |
Well, I don't see any obvious problem in the diff. Needs more thorough debugging... |
I think I know what's going on here: The bug only occurs for check builds and for those we don't encode MIR in crate metadata. That was no problem so far because we didn't run @nagisa I suppose you can add an early exit to |
@nagisa, do you want to look into a fix or should I? Either option is fine with me. |
Either way works for me, i imagine adding a check like described is okay
and is a trivial change to make. i can do it tonight but feel free to do it
first if it is critical to have it solved sooner rather than later.
…On Wed, Feb 20, 2019, 17:09 Michael Woerister ***@***.*** wrote:
@nagisa <https://github.com/nagisa>, do you want to look into a fix or
should I? Either option is fine with me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#58323 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AApc0gtcCg58-_jevfNObYSXkgSxL6n2ks5vPWVEgaJpZM4aykmZ>
.
|
…oerister Use informational target machine for metadata Since there is nothing to optimise there... Should fix rust-lang#58323 but haven’t tested locally. r? @michaelwoerister
…oerister Use informational target machine for metadata Since there is nothing to optimise there... Should fix rust-lang#58323 but haven’t tested locally. r? @michaelwoerister
…oerister Use informational target machine for metadata Since there is nothing to optimise there... Should fix rust-lang#58323 but haven’t tested locally. r? @michaelwoerister
…oerister Use informational target machine for metadata Since there is nothing to optimise there... Should fix rust-lang#58323 but haven’t tested locally. r? @michaelwoerister
…oerister Use informational target machine for metadata Since there is nothing to optimise there... Should fix rust-lang#58323 but haven’t tested locally. r? @michaelwoerister
This is now on beta |
Use informational target machine for metadata Since there is nothing to optimise there... Should fix #58323 but haven’t tested locally. r? @michaelwoerister
Reproduction: https://github.com/jonas-schievink/ice-mono-item
The text was updated successfully, but these errors were encountered: