Hello,

i cross-checked in trunk the referenced ${cpu_type}'s from ${target} in configure.ac
against the list of possible CPU types from install.texi, lines 876--885
(under 'Here are the possible CPU types:').

@quotation
aarch64, aarch64_be, alpha, alpha64, amdgcn, arc, arceb, arm, armeb, avr, bfin,
bpf, cris, csky, epiphany, fido, fr30, frv, ft32, h8300, hppa, hppa2.0,
hppa64, i486, i686, ia64, iq2000, lm32, loongarch64, m32c, m32r, m32rle, m68k,
mcore, microblaze, microblazeel, mips, mips64, mips64el, mips64octeon,
mips64orion, mips64vr, mipsel, mipsisa32, mipsisa32r2, mipsisa64, mipsisa64r2,
mipsisa64r2el, mipsisa64sb1, mipsisa64sr71k, mipstx39, mmix, mn10300, moxie,
msp430, nds32be, nds32le, nvptx, or1k, pdp11, powerpc, powerpc64,
powerpc64le, powerpcle, pru, riscv32, riscv32be, riscv64, riscv64be, rl78, rx,
s390, s390x, sh, shle, sparc, sparc64, tic6x, v850,
v850e, v850e1, vax, visium, x86_64, xstormy16, xtensa
@end quotation

The configure.ac script uses also these (probably outdated?) CPU types not mentioned above:
(lines 619, 640, 913, 1329, ...) rs6000
(lines 877, 983) crisv32
(lines 986, 989, 992, 1296) kvx
(line  1004) m68hc11, m6811, m68hc12, m6812
(line  1194) c4x, tic4x
(line  1197) tic54x
(lines 1200, 3118) d10v
(lines 1203, 3115) d30v
(line  1215) h8300
(line  1218) h8500
(line  1221) hppa1.1
(line  1243) i960
(line  3065) spu
(line  3855) mep*
(multiple lines) i[35789]86

(This is the result of checks for ${target} and ${cpu_type}).
Sorry, no patch, as I am not confident with changing something here...

Heiko

Reply via email to