This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: proper way to include gcc/config/<arch>/<arch>.h ?
- To: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
- Subject: Re: proper way to include gcc/config/<arch>/<arch>.h ?
- From: "David O'Brien" <obrien at FreeBSD dot org>
- Date: Mon, 14 May 2001 15:54:40 -0700
- Cc: gcc at gcc dot gnu dot org
- Organization: The NUXI BSD group
- References: <10105142234.AA18849@vlsi1.ultra.nyu.edu>
- Reply-To: obrien at FreeBSD dot org
On Mon, May 14, 2001 at 06:34:15PM -0400, Richard Kenner wrote:
> What is the proper way to include gcc/config/<arch>/<arch>.h?
>
> `tm_file' is set early in `config.gcc' as
> "tm_file=${cpu_type}/${cpu_type}.h", however some config triplets add to
> `tm_file' by "tm_file="${tm_file} foo.h", while others totally
> overwrite it with tm_file="foo.h <arch>/<arch>.h bar.h". Others do all
> kinds of things -- "*-*-gnu*" is a good example of this.
..snip..
> It depends on the structure of the port's files.
Is there a prefered way one should strive for (say new platforms or
header cleanup)?
--
-- David (obrien@FreeBSD.org)