Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!gorodish!guy From: guy%gorodish@Sun.COM (Guy Harris) Newsgroups: comp.unix.wizards Subject: Re: Big Programs Hurt Performance Message-ID: <29557@sun.uucp> Date: Wed, 30-Sep-87 13:49:35 EDT Article-I.D.: sun.29557 Posted: Wed Sep 30 13:49:35 1987 Date-Received: Sun, 4-Oct-87 21:19:29 EDT References: <1665@ncr-sd.SanDiego.NCR.COM) <8579@utzoo.UUCP) <6886@eddie.MIT.EDU) <4774@ncoast.UUCP> Sender: news@sun.uucp Lines: 17 > in order to assign two structures, the template used by pcc might be to > call a function to do a byte copy, but the Vax has an instruction to do the > copy... ...which code generated by PCC uses. Not a good example. > This kind of thing is the reason why e.g. Plexus is now compiling their > kernels using the Green Hills native 68020 compiler rather than pcc, Is not the Green Hills compiler an optimizing compiler (i.e., offering more optimization than the standard VAX UNIX peephole optimizer), and is it not also available for other machines (e.g., the NS32K series)? I don't know that non-retargetable compilers are necessarily that much better than retargetable ones, these days. Guy Harris {ihnp4, decvax, seismo, decwrl, ...}!sun!guy guy@sun.com