Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!usc!elroy.jpl.nasa.gov!decwrl!shelby!portia!name From: name@portia.Stanford.EDU (tony cooper) Newsgroups: comp.unix.aux Subject: Re: Good A/UX Compilers (was Re: Free Fortran for A/UX) Keywords: f2c Message-ID: <10932@portia.Stanford.EDU> Date: 8 Apr 90 06:44:54 GMT References: <10786@portia.Stanford.EDU> <1487@nems.dt.navy.mil> <1881@sequent.cs.qmw.ac.uk> Sender: tony cooper Organization: Stanford University Lines: 41 In article <1881@sequent.cs.qmw.ac.uk> liam@cs.qmw.ac.uk (William Roberts) writes: >The gcc compiler is a great deal better than the standard A/UX >C compiler - it is also better than the standard Sun C In addition to cc and gcc there is the Green Hills C compiler ported to A/UX by Unisoft. Here are dhrystone figures for the three on my machine: 7009 cc -O 8522 gcc -O (GNU) 9868 gcc (Green Hills) How do they compare for floating point calculations? Here are Whetstones (double precision): 1330 cc -O 2090 gcc -O (GNU) 2520 gcc (Green Hills) How about floating point performance using Linpack? For double precision using rolled BLAS we get in kflops: ---- cc -O (wouldn't compile, ran out of tree space) 259 gcc -O (GNU) 273 gcc (Green Hills) The Green Hills compiler does a good job of putting in inline 68881/2 floating point calls. the GNU compiler is faster when -fstrength-reduce is not used. How about Fortran compilers? There is a Green Hills f77 optimizing compiler, the A/UX 1.1 Fortran compiler and f2c which converts Fortran to C. Here are the double precision kflops for Linpack: 193 f77 -O 251 gf77 (Green Hills) To use f77 -O requires editing link assembly statements into link.l otherwise the optimizer chokes. Tony Cooper tony@popserver.stanford.edu