In #127877 @rejyr noticed tests/run-make/print-target-list was failing for csky-unknown-linux-gnuabiv2 (and other experimental llvm components) on the x86_64-gnu-llvm-17 CI builder with
# snip
error: could not create LLVM TargetMachine for triple: csky-unknown-linux-gnuabiv2: No available targets are compatible with triple "csky-unknown-linux-gnuabiv2"
# snip
#125702 (specifically #125702 (comment)) it was already noticed that tests/run-make/print-target-list seemed to fail for csky-unknown-linux-gnuabiv2.
Is this expected? Or what is the expected test behavior when
rustc --target csky-unknown-linux-gnuabiv2 --print sysroot
is ran (on the x86_64-gnu-llvm-17 CI builder)?
Or is it expected that we should skip trying to run this check for the csky-unknown-linux-gnuabiv2 and other experimental llvm component targets?
Update: this is also true for experimental llvm components avr, m68k, csky and xtensa, not too sure what the correct behavior is. Currently these targets are skipped by print-target-list's --print=sysroot check.
In #127877 @rejyr noticed
tests/run-make/print-target-listwas failing forcsky-unknown-linux-gnuabiv2(and other experimental llvm components) on thex86_64-gnu-llvm-17CI builder with#125702 (specifically #125702 (comment)) it was already noticed that
tests/run-make/print-target-listseemed to fail forcsky-unknown-linux-gnuabiv2.Is this expected? Or what is the expected test behavior when
is ran (on the
x86_64-gnu-llvm-17CI builder)?Or is it expected that we should skip trying to run this check for the
csky-unknown-linux-gnuabiv2and other experimental llvm component targets?Update: this is also true for experimental llvm components
avr,m68k,cskyandxtensa, not too sure what the correct behavior is. Currently these targets are skipped byprint-target-list's--print=sysrootcheck.