This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Guessing HP architecture?



I've been interested in identifying the HP-UX archictecture better myself, the
email below 
is from my suggestion of using sched.models. Also sched.models tracks is updated
with 
installation of the unbundled compiler in /opt/langtools/lib/sched.models and on
our
10.20 K380 didn't recognize it as a HPPA2.0 machine.

The sysconf(_SC_CPU_VERSION) approach already used by  the Hitachi triplet in
config.guess could easily be generalized to work with HP-UX  as well, and
correctly identifies
our K380. I was hoping for some feedback on this before doing it. I'd suggest
#ifdef-ing
around the PA_RISC{1_{1,2},2_0}  case and maybe even the PA_RISC_1_0 case if
you wish to try to use it even for the old Motorola CPU machines.

--- Jerry wrote
 
I'm looking a bit at adding HPPA 2.0 hooks into the compiler and am
looking at config.guess.  The model number-based selection criterion has
a problem.  Our V-class HPUX 11 box has model number 800.  This is a 2.0
machine.  But looking in the sched.models file on an HPUX 9 machine, I
see that 800 is an old 1.0 machine.  Model number 700 also has the same
problem.  Unless support for old 1.0 machines is going to be dropped, we
need something a bit more sophisticated.

An easy way to determine the architecture is using the file
sched.models.  Is this safe?  Is it available on all HPUX machines?  All
the machines we have have it, but those are only 9.x, 10.x and 11.x
machines.

Alternatively, those two model numbers could just be trapped and checked
against OS version.

-- 
Jerry Quinn                             Tel: (514) 761-8737
jquinn@nortel.ca                        Fax: (514) 761-8505
Speech Recognition Research

____________________Reply Separator____________________
Subject:    Re[2]: Suggested patch to egcs-19981019/config.guess => auto
Author: Rodney Brown
Date:       28/10/98 17:51

We have /usr/lib/sched.models on HP-UX 9.04 - but we also have the unbundled C
compiler
which is why I thought it was shipped by default on HP-UX 9.

Neither the {/usr,/opt/langtools}/lib/sched.models recognized our new box which
/usr/bin/model (also new on 10) gives as 9000/800/K380 .
sysconf(_SC_CPU_VERSION) correctly sees it as CPU_PA_RISC2_0

Generalizing the C program from the 3050*:HI-UX:*:* case could allow
config.guess to correctly identify the HPPA version on both HI-UX
and HP-UX, without autoconf needing changes for new HP models.
sysconf(_SC_CPU_VERSION) works on both the HP-UX 9.04 box and the
HP-UX 10.20 box I have accessable.

HP defines their CPU_... constants in /usr/include/sys/unistd.h
On  9.04  CPU_{HP_MC680{2,3,4}0,PA_RISC{1_{0,1},2_0}}
On 10.20  CPU_{HP_MC680{2,3,4}0,PA_RISC{1_{0,1,2},2_0}}

In view of the definitions for Motorola processors I'd be surprised
if it didn't work on HP-UX 8 and maybe even on the 300 series boxes
the current test recognizes.

Worth doing?

I'd also suggest changing the triplet for the *9??*:MPE/iX:*.* case
from hppa1.0-hp-mpeix to hppa1.1-hp-mpeix, since hppa1.0 boxes would be
infeasibly expensive to keep on maintenance by now - so I'd expect
MPE/iX to be running only on HPPA1.1 & HPPA2.0 boxes. As at MPE/iX5.5
(C.55.00 C.05.08) /usr/include/unistd.h doesn't define _SC_CPU_VERSION so the
suggestion above won't work for MPE/iX

____________________Reply Separator____________________
Subject:    Re: Suggested patch to egcs-19981019/config.guess => autocon
Author: Torbjorn Granlund <tege@matematik.su.se> 
Date:       23/10/98 11:48

The sched.models file is new in HP-UX 10.
It would be unwise to make config.guess dependent on it,
at least unconditionally.

Torbjörn





Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]