Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!CMR001.BITNET!Jacques_Gelinas
From: Jacques_Gelinas@CMR001.BITNET
Newsgroups: comp.sys.apollo
Subject: RE: 68k compiler target defaults
Message-ID: <900715.20155735.017211@CMR.CP6>
Date: 16 Jul 90 01:15:56 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 39


             >>           add "-A cpu,3000" to the CFLAGS
             >>          (I wish Apollo would make this the default)
>    Interesting.  Are you doing this for performance reasons?

I have also been doing this "customer" optimisation dozen of times.
Since i am lucky to be able to use a DN4000, i want to take full
advantage of it (even if it is like a DN3000). Otherwise, why pay
extra for advaced machines when the software ignores their features?

>               This is going to be a potentially confusing issue for our
>               customers who use our compilers

Indeed. But if they survived through the GPR routines changes (&status)
they should accept this.

>               we preserved all existing "-cpu" options,

Thanks! Very good (see my remark about GPR above).

>               Second, we added three new "-cpu" options
>               mathchip, mathlib and mathlib_sr10.

No, thanks. This is not enough. As a simple user -who complains a lot-
i want an internal flag to be turned on during the installation
procedure telling the compiler what machines are on my networrk
(many DN3500, 3 DN4000 ). The compiler should adjust its complicated
flags automagically based on this information. Of course:
- The individual users can overwrite this on the command line
- The hpollo supplied scripts would have to be rewritten to supply
  all the flags instead of relying on these varying defaults.
- Third party software developpers would also have to modify their
  scripts if they want the generic compiler (to avoid -O bugs, say).

DO NOT ASSUME THAT ORDINARY USERS READ SOFTWARE RELEASE NOTES PLEASE.
(There is too much to be done after installation to spend 3 hours
 on this, according to me..., and once it works, why bother?)

Hope i have been direct enough to avoid wasting bandwidth.