Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!umich!terminator!dabo.ifs.umich.edu!rees
From: rees@dabo.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: 68k compiler target defaults
Message-ID: <1990Jul19.013638.7920@terminator.cc.umich.edu>
Date: 19 Jul 90 01:36:38 GMT
References: <900715.20155735.017211@CMR.CP6> <4ba03a18.20b6d@apollo.HP.COM> <4ba189ba.12c9a@digital.sps.mot.com> <4ba5b9c8.20b6d@apollo.HP.COM>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 21

In article <4ba5b9c8.20b6d@apollo.HP.COM>, rehrauer@apollo.HP.COM (Steve
Rehrauer) writes:
  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?

The only saus that aren't necessarily built with the correct target machine
type are sau2 and sau3, which are both shared by 010 and 020 machines
(dn300/330 and dsp80/90).  These are built for 010 target.

I once built a sau2/aegis compiled for 020.  I couldn't notice any
difference in size or performance, but I didn't actually measure it.

Since there is no floating point in aegis I wouldn't expect it to make a lot
of difference.

You might see some improvement by compiling everything else with the correct
-cpu, but then Apollo would have to ship two sets of software, you would
have to worry about booting 010 nodes diskless off of 020 nodes, and it
would be a big headache.