Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] __hp9000s700 predefined
Date: Wed, 11 Oct 2000 00:04:01 -0700 (PDT)	[thread overview]
Message-ID: <200010110704.AAA05911@milano.cup.hp.com> (raw)

Hi all,
I was looking at how to properly ifdef code for parisc-linunx
and it seems that "#ifdef __hppa__" is "the right way" to do this.

Currently two files use ifdef CONFIG_PARISC: genrtc.c and hilkdb.c
Randolf (tausq) is fixing genrtc.c.
Any volunteers (ie 715/50 or 715/33 owners) for hilkdb.c?

But Randolf also noted that gcc predefines a few other things:
	-D__hp9000s700 -D_PA_RISC1_1

John Marvin suggested we remove the __hp9000s700 from the pa-linux
config files since it's HPUX crud. I think he's right since parisc-linux
kernels are intended to run on both 700's and 800's.
parisc-linux configs functionality in/out based on CONFIG_XXX flags
or run-time checks (ie register_driver()).
Can we remove the "-D__hp9000s700" from gcc/gcc/config/pa/pa-linux.h?

Similarly, gcc/gcc/config/pa/pa-linux64.h has "-D__hp9000s800"
which could/should be removed at the same time.

Any other thoughts on this?

thanks,
grant

             reply	other threads:[~2000-10-11  6:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-11  7:04 Grant Grundler [this message]
2000-10-11 14:44 ` [parisc-linux] __hp9000s700 predefined David Huggins-Daines
2000-10-11 15:31 ` John David Anglin
2000-10-11 16:54   ` Grant Grundler
2000-10-11 19:44     ` John David Anglin
2000-10-11 20:21       ` Grant Grundler
2000-10-11 20:21         ` John David Anglin
2000-10-11 22:15         ` John David Anglin
2000-10-11 22:45           ` Grant Grundler
     [not found] <no.id>
2000-10-11 20:11 ` John David Anglin

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=200010110704.AAA05911@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.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