Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site utah-cs.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!utah-cs!brownc
From: brownc@utah-cs.UUCP (Eric C. Brown)
Newsgroups: net.lang.c
Subject: Re: Re: Un-alignment in structures
Message-ID: <3274@utah-cs.UUCP>
Date: Sat, 6-Apr-85 15:41:01 EST
Article-I.D.: utah-cs.3274
Posted: Sat Apr  6 15:41:01 1985
Date-Received: Mon, 8-Apr-85 01:08:12 EST
References: <230@tellab2.UUCP> <135@mit-athena.UUCP> <5399@utzoo.UUCP> <7170@watdaisy.UUCP> <491@lll-crg.ARPA> <173@geowhiz.UUCP>
Reply-To: brownc@utah-cs.UUCP (Eric C. Brown)
Organization: Univ of Utah CS Dept
Lines: 21

In article <173@geowhiz.UUCP> karsh@geowhiz.UUCP (Bruce Karsh) writes:
>>> If you have to remove one millisecond from a tight loop that has to run
>>> in 50 milliseconds, you really should use assembly.
>> 
>> If you can possibly do it in assembly then an optimizing compiler that
>> generates good code can do it just as fast and you gain portability.
>
>  Can somebody *PROVE* this.  I don't think it's true.  I think a better
>statement would be that an optimizing compiler *might* be able to generate
>code that is as fast.  (And then again it might not be able to.)
>
Well, you may not be able to write it in C, but BLISS routinely generates
code that is much better than the code that most programmers generate.

Try reading "The Design of an Optimizing Compiler", by William Wulf et al.

Eric C. Brown
brownc@utah-cs
...!seismo!utah-cs!brownc

Execute People, not Programs!!