[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: More recognizing NetBSD CPUs (Super-H, MIPS 64bit)
|
From: |
Ben Elliston |
|
Subject: |
Re: More recognizing NetBSD CPUs (Super-H, MIPS 64bit) |
|
Date: |
Fri, 4 Jan 2019 21:05:17 +1100 |
|
User-agent: |
NeoMutt/20170609 (1.8.3) |
On Thu, Jan 03, 2019 at 04:41:25PM +0000, address@hidden wrote:
> The notable difference is that "shl", chosen for netbsd/sh by
> config.guess, is now recognised.
> @@ -1230,8 +1230,7 @@ case $cpu-$vendor in
> | riscv | riscv32 | riscv64 \
> | rl78 | romp | rs6000 | rx \
> | score \
> - | sh | sh[1234] | sh[24]a | sh[24]ae[lb] | sh[23]e |
> she[lb] | sh[lb]e \
> - | sh[1234]e[lb] | sh[12345][lb]e | sh[23]ele | sh64 |
> sh64le \
> + | sh | sh[123456789lbe]* | sh64 | sh64le \
> | sparc | sparc64 | sparc64b | sparc64v | sparc86x |
> sparclet \
> | sparclite \
> | sparcv8 | sparcv9 | sparcv9b | sparcv9v | sv1 | sx* \
I don't understand what this patch is doing -- sh1 is already
recognised:
$ sh config.sub sh1-netbsd5.0
sh1-unknown-netbsd5.0
I don't want config.sub to recognise sh[0-9]. That is wrong --
config.sub should only recognise real SH machines.
Ben
signature.asc
Description: PGP signature