Skip to content

perform sanity checks before initiating cross-compilation in MirOpt #118050

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

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions src/bootstrap/src/core/build_steps/test.rs
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ use crate::core::builder::{Builder, Compiler, Kind, RunConfig, ShouldRun, Step};
use crate::core::config::flags::get_completion;
use crate::core::config::flags::Subcommand;
use crate::core::config::TargetSelection;
use crate::core::sanity::Finder;
use crate::utils;
use crate::utils::cache::{Interned, INTERNER};
use crate::utils::exec::BootstrapCommand;
Expand Down Expand Up @@ -1527,6 +1528,16 @@ You can add that mapping by changing MIR_OPT_BLESS_TARGET_MAPPING in src/bootstr
});

for target in targets {
if !builder.config.dry_run() {
let mut cmd_finder = Finder::new();

cmd_finder.must_have(builder.cc(target));

if let Some(ar) = builder.ar(target) {
cmd_finder.must_have(ar);
}
}

run(target);

let panic_abort_target = builder.ensure(MirOptPanicAbortSyntheticTarget {
Expand Down