Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site im4u.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!ut-sally!im4u!fletcher From: fletcher@im4u.UUCP Newsgroups: net.lang.c Subject: Re: more questions about efficient C code Message-ID: <328@im4u.UUCP> Date: Tue, 2-Jul-85 18:24:34 EDT Article-I.D.: im4u.328 Posted: Tue Jul 2 18:24:34 1985 Date-Received: Thu, 4-Jul-85 00:42:46 EDT References: <474@crystal.UUCP> <420@enmasse.UUCP> <2367@sun.uucp> Reply-To: fletcher@im4u.UUCP (Fletcher Mattox) Distribution: net Organization: U. Texas CS Dept., Austin, Texas Lines: 19 In article <2367@sun.uucp> jfarrell@sun.UUCP (Jerry Farrell) writes: >> >>One is to write a simple test program and use the '-S' >>flag of the compiler. > >Unfortunately, this option is not likely to show you the >optimized code you would get from running the compiler with >the -O flag. To really see what's being generated, compile >it, and then look at the object file with something like >foo,24?ai >in adb. Adb to see if your code is optimized? Now that's real masochism. Just do 'cc -O -S foo.c'. This fails if you do 'cc -OS foo.c', which is probably what you were refering to. This is with 4.2's compiler. -- Fletcher Mattox, fletcher@ut-sally.ARPA, {ihnp4,seismo,ctvax}!ut-sally!fletcher