Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!unido!sns!space
From: space@sns.UUCP (Lars Soltau)
Newsgroups: comp.lang.c
Subject: Re: Efficient Coding Practices
Summary: yet another lesson
Message-ID: <222@sns.UUCP>
Date: 4 Oct 88 20:22:58 GMT
References: <8809191521.AA17824@ucbvax.Berkeley.EDU> <68995@sun.uucp> <23025@amdcad.AMD.COM> <607@ardent.UUCP> <836@proxftl.UUCP> <34112@XAIT.XEROX.COM> <846@proxftl.UUCP> <34196@XAIT.Xerox.COM>
Reply-To: space@sns.UUCP (Lars Soltau)
Organization: Stuttgart Net System
Lines: 11

In article <34196@XAIT.Xerox.COM> g-rh@XAIT.Xerox.COM (Richard Harter) writes:
>Lesson:  If one is optimizing code one has to think about what the machine
>will have to do in different implementations when comparing them.

Lesson: never optimize C code if you have not written the compiler yourself,
it's far easier and safer to optimize the assembler code.
-- 
Lars Soltau	UUCP: uunet!unido!sns!spcnet!space	BIX: -- no bucks --

Here's looking at you, kid!
		-- the Medusa