I'm not a compiler hacker (they're nice black boxes that take my C code and
turn it into executables), but isn't this sort of problem detected in the
front end of the compiler which is nominally supposed to be the same on all
platforms (i.e. it's parsing C, not generating the platform-specific code)?
It strikes me as very odd that this kind of bug would only show up on m68k.

This also begs the question about the code in /usr/src/bin/pax that gcc on
m68k won't compile without warnings; presumably all m68k ports (e.g. sun3,
mac68k, amiga, atari, hp300) will not build until gcc is fixed or this code
has a work-around put in it.

	Erik <fair@clock.org>