Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jason R Thorpe <thorpej@wasabisystems.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: HPPA files naming convention...
Date: Mon, 25 Nov 2002 17:08:00 -0000	[thread overview]
Message-ID: <20021126010858.GE21009@yeah-baby.shagadelic.org> (raw)
In-Reply-To: <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>


  parent reply	other threads:[~2002-11-26  1:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25 16:56 Joel Brobecker
2002-11-25 16:59 ` Daniel Jacobowitz
2002-11-25 17:08 ` Jason R Thorpe [this message]
2002-11-25 22:19 ` Eli Zaretskii
2002-11-26  7:30 ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021126010858.GE21009@yeah-baby.shagadelic.org \
    --to=thorpej@wasabisystems.com \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox