Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!ll-xn!mit-eddie!uw-beaver!ssc-vax!uvicctr!sdean1
From: sdean1@uvicctr.UUCP (Steven A. Dean)
Newsgroups: comp.sys.amiga
Subject: Re: Assembly for graphics
Message-ID: <384@uvicctr.UUCP>
Date: 30 Mar 88 22:31:55 GMT
References: <2734@crash.cts.com> <3013@gryphon.CTS.COM>
Reply-To: sdean1@uvicctr.UUCP (Steven A. Dean)
Followup-To: alt.flame
Organization: University of Victoria, Victoria B.C. Canada
Lines: 29
Keywords: Assembly Small Fast BETTER
Summary: Well, sorta....

In article <3013@gryphon.CTS.COM> richard@gryphon.CTS.COM (Richard Sexton) writes:
>Ok, now LISTEN this time.
>
>"If the programmer knows their compiler, knows their machine, and knows what
>they are doing, the speed penalty for using C is very small".
>[...]
                                                 ^^^^^^^^^^^^
------------------------------------------------------|||
Yes!  BUT! Sometimes very small isn't good enough!  Besides, if you write a 
lot in assembly, you can produce code that's smaller (almost always) and
runs faster (always, unless you are awful at assembly).  You also have to
learn ALL of the idiocyncrasies (sp?) of your compiler before you can 
make your code jump through loops... with an assembler (even one that
does you *favours* like converting move.l #0,d0 to moveq #0,d0) you just 
need to know your assembly.  Period.

												-Steve

>-- 
>..who come from long lines of soldiers,  | richard@gryphon.CTS.COM
>whose duty was fulfilled,                | ihnp4!scgvaxd!cadovax!gryphon!richard
>in the words of the warriors will,       | rutgers!marque!gryphon!richard
>and protocol.                            | codas!ddsw1!gryphon!richard

--
Steven A. Dean
sdean1@uvunix.BITNET
sdean1@uvunix.UVic.CDN
...uw-beaver!uvicctr!sdean1
...ubc-vision!uvicctr!sdean1