[PATCH] Add m68k-uclinux target

[Zack Weinberg]

Hans-Peter Nilsson <hp@bitrange.com> writes:

> On Wed, 17 Sep 2003, Zack Weinberg wrote:
>
>> I would encourage you NOT to introduce redundancy into
>> the configuration triple by using CPU-*-uclinux-uclibc.
>
> There's no redundancy.  CPU-*-linux-uclibc is truly different
> from CPU-*-uclinux-uclibc.  The latter has all sorts of
> restrictions due to the lack of MMU while the former is only
> restricted by uclibc. ;-)  Yes, they both exist in the real
> world.

Okay, but do any of these restrictions affect the default code
generation that gcc should be doing?  More generally, do any of
them affect the way user space code needs to operate?

zw