e72e7e9ae3
`CompilerError` has `CompilationFailed` and `ICE` variants, which seems reasonable at first. But the way it identifies them is flawed: - If compilation errors out, i.e. `RunCompiler::run` returns an `Err`, it uses `CompilationFailed`, which is reasonable. - If compilation panics with `FatalError`, it catches the panic and uses `ICE`. This is sometimes right, because ICEs do cause `FatalError` panics, but sometimes wrong, because certain compiler errors also cause `FatalError` panics. (The compiler/rustdoc/clippy/whatever just catches the `FatalError` with `catch_with_exit_code` in `main`.) In other words, certain non-ICE compilation failures get miscategorized as ICEs. It's not possible to reliably distinguish the two cases, so this commit merges them. It also renames the combined variant as just `Failed`, to better match the existing `Interrupted` and `Skipped` variants. Here is an example of a non-ICE failure that causes a `FatalError` panic, from `tests/ui/recursion_limit/issue-105700.rs`: ``` #![recursion_limit="4"] #![invalid_attribute] #![invalid_attribute] #![invalid_attribute] #![invalid_attribute] #![invalid_attribute] //~^ERROR recursion limit reached while expanding fn main() {{}} ```
86 lines
2.5 KiB
Rust
86 lines
2.5 KiB
Rust
// run-pass
|
|
// Test StableMIR behavior when different results are given
|
|
|
|
// ignore-stage1
|
|
// ignore-cross-compile
|
|
// ignore-remote
|
|
// ignore-windows-gnu mingw has troubles with linking https://github.com/rust-lang/rust/pull/116837
|
|
// edition: 2021
|
|
|
|
#![feature(rustc_private)]
|
|
#![feature(assert_matches)]
|
|
|
|
#[macro_use]
|
|
extern crate rustc_smir;
|
|
extern crate rustc_driver;
|
|
extern crate rustc_interface;
|
|
extern crate stable_mir;
|
|
|
|
use rustc_smir::rustc_internal;
|
|
use std::io::Write;
|
|
|
|
/// This test will generate and analyze a dummy crate using the stable mir.
|
|
/// For that, it will first write the dummy crate into a file.
|
|
/// Then it will create a `StableMir` using custom arguments and then
|
|
/// it will run the compiler.
|
|
fn main() {
|
|
let path = "input_compilation_result_test.rs";
|
|
generate_input(&path).unwrap();
|
|
let args = vec!["rustc".to_string(), path.to_string()];
|
|
test_continue(args.clone());
|
|
test_break(args.clone());
|
|
test_failed(args.clone());
|
|
test_skipped(args.clone());
|
|
test_captured(args)
|
|
}
|
|
|
|
fn test_continue(args: Vec<String>) {
|
|
let result = run!(args, || ControlFlow::Continue::<(), bool>(true));
|
|
assert_eq!(result, Ok(true));
|
|
}
|
|
|
|
fn test_break(args: Vec<String>) {
|
|
let result = run!(args, || ControlFlow::Break::<bool, i32>(false));
|
|
assert_eq!(result, Err(stable_mir::CompilerError::Interrupted(false)));
|
|
}
|
|
|
|
#[allow(unreachable_code)]
|
|
fn test_skipped(mut args: Vec<String>) {
|
|
args.push("--version".to_string());
|
|
let result = run!(args, || unreachable!() as ControlFlow<()>);
|
|
assert_eq!(result, Err(stable_mir::CompilerError::Skipped));
|
|
}
|
|
|
|
#[allow(unreachable_code)]
|
|
fn test_failed(mut args: Vec<String>) {
|
|
args.push("--cfg=broken".to_string());
|
|
let result = run!(args, || unreachable!() as ControlFlow<()>);
|
|
assert_eq!(result, Err(stable_mir::CompilerError::Failed));
|
|
}
|
|
|
|
/// Test that we are able to pass a closure and set the return according to the captured value.
|
|
fn test_captured(args: Vec<String>) {
|
|
let captured = "10".to_string();
|
|
let result = run!(args, || ControlFlow::Continue::<(), usize>(captured.len()));
|
|
assert_eq!(result, Ok(captured.len()));
|
|
}
|
|
|
|
fn generate_input(path: &str) -> std::io::Result<()> {
|
|
let mut file = std::fs::File::create(path)?;
|
|
write!(
|
|
file,
|
|
r#"
|
|
// This should trigger a compilation failure when enabled.
|
|
#[cfg(broken)]
|
|
mod broken_mod {{
|
|
fn call_invalid() {{
|
|
invalid_fn();
|
|
}}
|
|
}}
|
|
|
|
fn main() {{}}
|
|
"#
|
|
)?;
|
|
Ok(())
|
|
}
|