From: "Kevin Carson" <Kevin_Carson@hp-canada-om1.om.hp.com>
To: <parisc-linux@thepuffingroup.com>
Subject: Re: [parisc-linux] H60
Date: Wed, 30 Jun 1999 18:20:27 -0700 [thread overview]
Message-ID: <00be01bec35f$e780f410$2119510f@vset33.canada.hp.com> (raw)
As I understand it,
second column consists of the PA-RISC instruction set revision (1.0, 1.1, or
2.0) and the letter indicates what type of CPU is running that revision in
the respective
box (CPU models being also the third column).
The point of all this is that the HP ANSI compiler takes both a instruction
revision the object code is targeted towards (the most portable being the
older revision 1.0 since all the revisions are backward compatible) and a
hint about which implementation the instruction scheduling optimizations
should be targeting (which does affect compatability in any way).
How much difference does the letter portion really make? From practical
experience not much, but it could! Which is the point of maintaining this
file in the first place. The instruction set revision makes a BIG
difference for later chips.
Kevin
-----Original Message-----
From: rrauenza@cup.hp.com <rrauenza@cup.hp.com>
To: adevries@thepuffingroup.com <adevries@thepuffingroup.com>
Cc: rrauenza@cup.hp.com <rrauenza@cup.hp.com>;
parisc-linux@thepuffingroup.com <parisc-linux@thepuffingroup.com>
Date: Tuesday, June 29, 1999 11:55 PM
Subject: Re: [parisc-linux] H60
>
>Apparently it exists in quite a few places!
>
>The second column is the PA-RISC version number. I'm not sure how
>significant the letters are in the version numbers.
>
>> Rich Rauenzahn wrote:
>> >
>> > Take a look at /usr/lib/sched.models on HP-UX -- it documents quite a
few
>> > models and PA-RISC versions.
>> >
>>
>> Oh, that's pretty interesting. I found sched.modules in
>> /usr/sam/lib/mo.
>>
>> What's the second column?
>>
>> - Alex
>
>---------------------------------------------------------------------------
>To unsubscribe: send e-mail to parisc-linux-request@thepuffingroup.com with
>`unsubscribe' as the subject.
>
next reply other threads:[~1999-07-01 5:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 1:20 Kevin Carson [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-06-30 17:26 [parisc-linux] H60 Davin Petersen
1999-06-30 21:38 ` Kirk Bresniker
1999-06-30 15:54 Davin Petersen
1999-06-30 17:27 ` Stan Sieler
1999-06-30 5:20 Mike Hibler
1999-06-29 23:51 Davin Petersen
1999-06-30 0:13 ` Stan Sieler
1999-06-30 0:43 ` Alex deVries
1999-06-30 0:53 ` Stan Sieler
1999-06-30 5:51 ` Rich Rauenzahn
1999-06-30 6:34 ` Alex deVries
1999-06-30 6:55 ` Richard J. Rauenzahn
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='00be01bec35f$e780f410$2119510f@vset33.canada.hp.com' \
--to=kevin_carson@hp-canada-om1.om.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