-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
"internal compiler error: unexpected panic" - when trying to run cargo test
on nightly and stable
#51516
Labels
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
Comments
cargo test
on nightly and stable
Update: I just tried to run the test on the stable toolchain, and get the same error
Versions:
|
bors
added a commit
that referenced
this issue
Jul 10, 2018
Store scalar pair bools as i8 in memory We represent `bool` as `i1` in a `ScalarPair`, unlike other aggregates, to optimize IR for checked operators and the like. With this patch, we still do so when the pair is an immediate value, but we use the `i8` memory type when the value is loaded or stored as an LLVM aggregate. So `(bool, bool)` looks like an `{ i1, i1 }` immediate, but `{ i8, i8 }` in memory. When a pair is a direct function argument, `PassMode::Pair`, it is still passed using the immediate `i1` type, but as a return value it will use the `i8` memory type. Also, `bool`-like` enum tags will now use scalar pairs when possible, where they were previously excluded due to optimization issues. Fixes #51516. Closes #51566. r? @eddyb cc @nox
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am working on a private project, and just discovered the following panic on the nightly compiler, when running
cargo test
Versions:
Operating System: macOS 10.13.3 (17D102)
The text was updated successfully, but these errors were encountered: