run abi/compatibility test against a whole bunch of targets

[RalfJung]

No description provided.

[rustbot]

r? @b-naber

(rustbot has picked a reviewer for you, use r? to override)

[RalfJung]

These look like false warnings:

/home/r/src/rust/rustc.2/tests/ui/abi/compatibility.rs: revision aarch64 should specify `needs-llvm-components:` as it has `--target` set
/home/r/src/rust/rustc.2/tests/ui/abi/compatibility.rs: revision arm should specify `needs-llvm-components:` as it has `--target` set
/home/r/src/rust/rustc.2/tests/ui/abi/compatibility.rs: revision loongarch64 should specify `needs-llvm-components:` as it has `--target` set
/home/r/src/rust/rustc.2/tests/ui/abi/compatibility.rs: revision mips should specify `needs-llvm-components:` as it has `--target` set
/home/r/src/rust/rustc.2/tests/ui/abi/compatibility.rs: revision mips64 should specify `needs-llvm-components:` as it has `--target` set
/home/r/src/rust/rustc.2/tests/ui/abi/compatibility.rs: revision nvptx64 should specify `needs-llvm-components:` as it has `--target` set
/home/r/src/rust/rustc.2/tests/ui/abi/compatibility.rs: revision powerpc64 should specify `needs-llvm-components:` as it has `--target` set
/home/r/src/rust/rustc.2/tests/ui/abi/compatibility.rs: revision riscv should specify `needs-llvm-components:` as it has `--target` set
/home/r/src/rust/rustc.2/tests/ui/abi/compatibility.rs: revision s390x should specify `needs-llvm-components:` as it has `--target` set
/home/r/src/rust/rustc.2/tests/ui/abi/compatibility.rs: revision sparc should specify `needs-llvm-components:` as it has `--target` set
/home/r/src/rust/rustc.2/tests/ui/abi/compatibility.rs: revision sparc64 should specify `needs-llvm-components:` as it has `--target` set
/home/r/src/rust/rustc.2/tests/ui/abi/compatibility.rs: revision wasm should specify `needs-llvm-components:` as it has `--target` set

We only do check-builds, so we don't need anything from LLVM here. Cc @nagisa

[bjorn3]

Even check builds still initialize the codegen backend. While the actual target is only selected when creating a target machine, which check builds skip, there are some target specific flags specified here like -enable-emscripten-cxx-exceptions. These may cause an error if the respective target is compiled out.

[RalfJung]

Ah, that is unfortunate, I would have hoped our front-end is less dependent on the codegen backend than that...

[wesleywiser]

Thanks @RalfJung! 💯

[wesleywiser]

@bors r+ rollup

[bors]

📌 Commit ec18811 has been approved by wesleywiser

It is now in the queue for this repository.