This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: HPPA files naming convention...
- From: Jason R Thorpe <thorpej at wasabisystems dot com>
- To: Joel Brobecker <brobecker at gnat dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Mon, 25 Nov 2002 17:08:58 -0800
- Subject: Re: HPPA files naming convention...
- Organization: Wasabi Systems, Inc.
- References: <20021126005631.GC23000@gnat.com>
On Mon, Nov 25, 2002 at 04:56:31PM -0800, Joel Brobecker wrote:
> I find the naming convention for the hppa targets too short for my
> liking: - hppah -> hppa on hpux
> - hppao -> hppa on osf
> - hppab -> hppa on bsd
>
> I suggest we transition to a more verbose naming, which should be more
> consistent with the other ports I know. For instance, how about
> hppa-hpux instead of hppah. I hear a netbsd port will probably be done
> in the future, we can then use hppa-netbsd.
>
> We would use this convention for the files in the config/pa directory
> (tm-hppa-hpux.h, hppa-hpux.mt, etc), and also for for the files in gdb
> (hppa-hpux-tdep.c).
The convention sort of varies based on OS ... NetBSD platforms use e.g.
alphanbsd-tdep.c vs. the Linux alpha-linux-tdep.c. .mt and .mh files
for NetBSD in the processor-specific directory are usually just called
e.g. alpha/nbsd.mh.
So, for your configurations, select whatever convention suits you. But
be prepared for other OS config conventions to creep into the mix at
some point :-)
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>