While reimplementing config.sub for use in a situation where no bash interpreter was available, I discovered several oddities about config.sub's behavior.
One such oddity was the fact that an explicitly-provided vendor will be clobbered by the inferred vendor for three cpu types: microblaze, s390, and mmix. This commit adds test cases for this clobbering behavior, so that unintentional changes to it will be noticed. --- testsuite/config-sub.data | 3 +++ 1 file changed, 3 insertions(+) diff --git a/testsuite/config-sub.data b/testsuite/config-sub.data index ba934b6..f034849 100644 --- a/testsuite/config-sub.data +++ b/testsuite/config-sub.data @@ -403,6 +403,7 @@ metag metag-unknown-none metag-linux metag-unknown-linux-gnu microblaze microblaze-xilinx-none microblaze-elf microblaze-xilinx-elf +microblaze-unknown-elf microblaze-xilinx-elf microblaze-linux microblaze-xilinx-linux-gnu microblazeel microblazeel-xilinx-none microblazeel-elf microblazeel-xilinx-elf @@ -486,6 +487,7 @@ mipstx39el mipstx39el-unknown-elf mmax ns32k-encore-bsd mmix mmix-knuth-mmixware mmix-elf mmix-knuth-elf +mmix-unknown-elf mmix-knuth-elf mn10200 mn10200-unknown-none mn10300 mn10300-unknown-none mon960 i960-intel-mon960 @@ -684,6 +686,7 @@ s390 s390-ibm-none s390-busybox-linux s390-busybox-linux-gnu s390-ibm-zvmoe s390-ibm-zvmoe s390-linux s390-ibm-linux-gnu +s390-unknown-elf s390-ibm-elf s390x s390x-ibm-none s390x-busybox-linux s390x-busybox-linux-gnu s390x-ibm-zvmoe s390x-ibm-zvmoe -- 2.41.0
