Why does config.guess come up with such wacky stuff?

[Joe Buck]

Jeff writes:
> For building our releases we override config.guess so that we can exercise
> more control over what systems the release will work on [...]
> But I consider this behavior the exception rather than the rule.
> 
> I agree 100% with Robert that config.guess is supposed to cater to the random
> person that picks up GCC (or other tools) off the net and wants to get it
> built with a minimum of hassle.

This means that in any case where config.guess can't be sure it has the
right answer, it should report a safe answer.  This will mean that it
might assume an older processor in some cases and not use the latest
instructions, but at least it will work.