-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
regression: could not fully normalize type #78139
Comments
Full error log:
|
I'll bisect this one |
Doesn't happen on the latest commit by
|
I can still reproduce with 9832374:
|
It may just be an instance of me not doing something right, I used:
|
The PR did introduce some additional uses of |
Both sites where it is used are of this pattern: if mem::needs_drop::<T>() {
unsafe {
ptr::drop_in_place(...);
}
} They're just there as hints to to let llvm DCE the drop_in_place earlier. So if needed removing them should be safe. |
Assigning |
Assigning myself to revert #70793 on beta (and potentially nightly, depending on if we can get a fix soon). |
Do we know if removing |
MCVE would be good, yes. |
I hit (what seems like) this ICE with |
Yes, it would be -- even if it's a separate issue we can just open that :) MCVE is always useful. |
@rustbot ping cleanup This issue needs an MVCE |
Hey Cleanup Crew ICE-breakers! This bug has been identified as a good cc @AminArria @camelid @chrissimpkins @contrun @DutchGhost @elshize @ethanboxx @h-michael @HallerPatrick @hdhoang @hellow554 @imtsuki @JamesPatrickGill @kanru @KarlK90 @LeSeulArtichaut @MAdrianMattocks @matheus-consoli @mental32 @nmccarty @Noah-Kennedy @pard68 @PeytonT @pierreN @Redblueflame @RobbieClarken @RobertoSnap @robjtede @SarthakSingh31 @shekohex @sinato @smmalis37 @steffahn @Stupremee @tamuhey @turboladen @woshilapin @yerke |
Here's my nightly Interestingly, it goes away when putting all of the code into one crate. Full error message (with
|
Hmm, this may be a distinct problem, but maybe not. Hard to tell. |
I'm re-adding the MCVE label because the crate on beta does not require features, so we should be able to come up with a non-nightly MCVE. (Also, it would be good to have a single-crate MCVE, but perhaps the multicrate nature is critical here?) |
cc #54114, which may be the same underlying bug (but pre-existing?) |
hey @Mark-Simulacrum , did you manage to land a revert of #70793 on beta (and nightly?)? |
If reverting the PR proves difficult more targeted options would be either removing the use of |
@nikomatsakis @pnkfelix Do we think given that we're likely to fix the regression here at least in #78845 and #78854 we should close this bug? Neither of those PRs fixes the underlying issue (whatever it is) since the lack of normalization is almost certainly still present, but we also don't have (AFAIK) a good test case here for the bug. |
…ulacrum [beta] try to work around type normalization regression This just removes the offending lines that trigger rust-lang#78139. I have doubts that this will actually solve the issue but it's simple enough to try. This PR needs a crater run for the failing crate.
@Mark-Simulacrum I expect so. |
dilbert-feed is ICEing on beta with error: internal compiler error: compiler/rustc_traits/src/normalize_erasing_regions.rs:37:32: could not fully normalize
<tokio::prelude::future::Either<tokio::prelude::future::Map<tokio::prelude::future::AndThen<tokio::prelude::future::AndThen<tokio::prelude::future::FutureResult<std::string::String, failure::Error>, std::result::Result<hyper::Uri, failure::Error>, [closure@src/main.rs:162:51: 162:96]>, tokio::prelude::future::Map<tokio::prelude::future::FromErr<tokio::prelude::future::AndThen<hyper::client::ResponseFuture, tokio::prelude::future::Map<tokio::prelude::stream::Concat2<hyper::Body>, [closure@src/main.rs:46:40: 46:62]>, fn(hyper::Response<hyper::Body>) -> impl hyper::rt::Future {concat_body}>, failure::Error>, [closure@src/main.rs:91:14: 95:10]>, [closure@src/main.rs:163:51: 163:92]>, [closure@src/main.rs:164:46: 167:42]>, tokio::prelude::future::FutureResult<ComicInfo, failure::Error>> as tokio::prelude::IntoFuture>::Future
https://crater-reports.s3.amazonaws.com/beta-1.48-1/beta-2020-10-09/gh/Soft.dilbert-feed/log.txt
The text was updated successfully, but these errors were encountered: