-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Compiler panic #56560
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Labels
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
Comments
This looks liked a duplicate of #51648, which has recently been fixed. |
@estebank when building with nightly, it work like a charm |
Great to hear! |
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Jan 7, 2019
This commit is an attempt to force `Instant::now` to be monotonic through any means possible. We tried relying on OS/hardware/clock implementations, but those seem buggy enough that we can't rely on them in practice. This commit implements the same hammer Firefox recently implemented (noted in rust-lang#56612) which is to just keep whatever the lastest `Instant::now()` return value was in memory, returning that instead of the OS looks like it's moving backwards. Closes rust-lang#48514 Closes rust-lang#49281 cc rust-lang#51648 cc rust-lang#56560 Closes rust-lang#56612 Closes rust-lang#56940
bors
added a commit
that referenced
this issue
Jan 8, 2019
std: Force `Instant::now()` to be monotonic This commit is an attempt to force `Instant::now` to be monotonic through any means possible. We tried relying on OS/hardware/clock implementations, but those seem buggy enough that we can't rely on them in practice. This commit implements the same hammer Firefox recently implemented (noted in #56612) which is to just keep whatever the lastest `Instant::now()` return value was in memory, returning that instead of the OS looks like it's moving backwards. Closes #48514 Closes #49281 cc #51648 cc #56560 Closes #56612 Closes #56940
bors
added a commit
that referenced
this issue
Jan 8, 2019
std: Force `Instant::now()` to be monotonic This commit is an attempt to force `Instant::now` to be monotonic through any means possible. We tried relying on OS/hardware/clock implementations, but those seem buggy enough that we can't rely on them in practice. This commit implements the same hammer Firefox recently implemented (noted in #56612) which is to just keep whatever the lastest `Instant::now()` return value was in memory, returning that instead of the OS looks like it's moving backwards. Closes #48514 Closes #49281 cc #51648 cc #56560 Closes #56612 Closes #56940
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Compiler panics while compiling
[I'm sorry to only to be able to give you a short description and I will likley not be able to dig deeper into this due to time constraints]
I installed rust/cargo on Windows 10 (aws machine) via rustup-init. As a test I tried to clone and build https://github.com/sharkdp/bat . This resulted in a compiler panic, which instructed me to open a bug here
I tried this code:
I expected to see this happen: bat being build
Instead, this happened: Compiler panic for option/result
Meta
cargo --version --verbose
:rustc --version --verbose
:[System.Environment]::OSVersion.Version
:Backtrace [excerpt]:
The text was updated successfully, but these errors were encountered: