This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] remove arm/unknown-elf.h
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: obrien at FreeBSD dot org
- Cc: gcc-patches at gcc dot gnu dot org, Richard dot Earnshaw at arm dot com
- Date: Thu, 06 Dec 2001 14:28:26 +0000
- Subject: Re: [PATCH] remove arm/unknown-elf.h
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> Every consumer of arm/unknown-elf.h immediately includes arm/elf.h (via
> tm_files). There are no consumers of arm/unknown-elf.h only.
> Thus arm/unknown-elf.h can be folded into arm/elf.h.
You can't reach this conclusion from your argument; it should be perfectly
possible to create an ELF target that uses elf.h, but doesn't want the
definitions in unknown-elf.h -- that is the guiding decision.
unknown-elf.h is supposed to contain the bits of an elf interface that
would normally be set by the OS: in this case there is no OS (it's
unknown). It seems bizarre to me that the arm-linux ports are including
So I don't think your patch is correct.
It seems to me that the abstractions in GCC for target CPU and OS are
horribly intermixed, and that it would be useful to try and tease these
apart somehow. Multi-architecture OSs such as Linux and *BSD are
revealing problems in this area that probably need some thought.