Path: utzoo!attcan!uunet!lll-winken!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!oakhill!dover!digital!chen
From: chen@digital.sps.mot.com (Jinfu Chen)
Newsgroups: comp.sys.apollo
Subject: Re: 68k compiler target defaults
Message-ID: <4baa6e8c.12c9a@digital.sps.mot.com>
Date: 18 Jul 90 15:19:08 GMT
References: <900715.20155735.017211@CMR.CP6> <4ba03a18.20b6d@apollo.HP.COM> <4ba189ba.12c9a@digital.sps.mot.com> <4ba5b9c8.20b6d@apollo.HP.COM>
Sender: news@digital.sps.mot.com
Organization: Motorola, Inc. SPS, Mesa, AZ
Lines: 51

In article <4ba5b9c8.20b6d@apollo.HP.COM> rehrauer@apollo.HP.COM (Steve Rehrauer) writes:
>In article <4ba189ba.12c9a@digital.sps.mot.com> chen@digital.sps.mot.com (Jinfu Chen) writes:
>>On a seperate issue, when are we going to see a version of Domain/OS
>>compiled with `020/030/040 option?
>
>It was my impression that the relevant SAU's for '020/'030/'040 machines
>_were_ being built with the appropriate -cpu settings.  I believe Domain
>was built -cpu 3000 for my DN4000 here.  Perhaps I'm mistaken.  Or do I
>misunderstand you?

I wasn't clear on this. What I meant is the utilies such as ones in /com
/usr/apollo/bin, etc. Yes you're correct in /sau*.

>> Perhaps at least all the compilers
>>should be made with the option? I serious doubt there're many pre-020
>>cpu nodes around.
>
>No, we didn't want to outright orphan all the older nodes.  There aren't
>many around, but enough to deserve some minimum level of support.  If we
>built the compilers -cpu mathlib_sr10, the older nodes couldn't run them
>at all.  It's one thing to sacrifice convenience of the few for sake of
>performance of the many; it's another to obsolete the few entirely.  We
>aren't quite there yet for the compilers.  (Ignoring for a moment the
>question of whether a DN320 would be able to do any meaningful work with
>recent compilers, given their present 'heft'...)

There is an alternative, although it may add some extra works to HP/Apollo.
You can distribute the -cpu mathlib_sr10 compilers as the default in
/usr/apollo/lib, and also make following available:

cc.m68k.any ftn.m68k.any pas.m68k.any

Better yet, use symbolic link:

cc.m68k		-> cc.m68k.020
ftn.m68k	-> ftn.m68k.020
pas.m68k	-> pas.m68k.020

and let user use /install/tools/config to decide which one (020 or any) 
should be installed as default. In this way, majority will get 
performance boot, and yet oldder hardwares still can use them 
(if they want :-).


-- 
Jinfu Chen                  (602)898-5338      |
Motorola, Inc.  SPS  Mesa, AZ                  |
 ...uunet!motsps!digital!chen                  |
chen@digital.sps.mot.com                       |
CMS: RXFR30 at MESAVM                          |
----------