Cleanups for the m68k backend

[Zack Weinberg]

Bernardo Innocenti <bernie@develer.com> writes:

> On Tuesday 08 July 2003 22:29, you wrote:
>
>  > > It would be very reasonable to do this.
>  >
>  > I'd like to inject a general plea for the removal of all <cpu> affixes
>  > from target headers.  m68k/elf.h is unambiguous, there is no need to
>  > call it m68k/m68k-elf.h or elf68k.h or anything like that.
>
>  I would generally agree on these policy _except_ for this particular
> case. You'll have a very hard time the day you see a source file
> doing:
>
>    #include "elf.h"
>
> You'll find multiple instances of that header in various places, including,
> but not limited to, the back-end. The current include path might be
> difficult to find and half buried in specs.

I disagree - this can only be gcc/config/elf.h or /usr/include/elf.h
(which latter should be included as <elf.h> to make it clear).
gcc/config/m68k will never be on the include path, unless this is an
include from a file inside m68k/ itself, and no headers should be
doing that (I realize that they do now; this is one of the problems
with that).

zw