Hi Ben, I am only interested in recognizing this case: shl-unknown-netbsdelf8.99
The bug report to prompt me to make this change is: http://gnats.netbsd.org/53825 The reason 'shl' is used, is due to this normalization in config.guess: *:NetBSD:*:*) ... sh3el) machine=shl-unknown ;; sh3eb) machine=sh-unknown ;; sh5el) machine=sh5le-unknown ;; >From code inspection, NetBSD/Super-H 'uname -p' will only ever return 'sh3el' or 'sh3eb'.* I get the impression that the desired normalization would be 'shle' for little-endian and 'sh' for big-endian. For unclear reason, 'shl' was used instead of 'shle' in config.guess. GCC handles both: # Note the 'l'; we need to be able to match e.g. "shle" or "shl". sh[123456789lbe]*-*-* | sh-*-*) I was over-eager to change things, being inspired by GCC's config.gcc. * Super-H 5 / sh64 had a very brief life, and almost no hardware was made. Although, due to patents expiring, there's renewed interest in FOSS Super-H variants. _______________________________________________ config-patches mailing list config-patches@gnu.org https://lists.gnu.org/mailman/listinfo/config-patches
