Path: utzoo!utgpu!water!watmath!clyde!rutgers!sunybcs!boulder!hao!husc6!bloom-beacon!oberon!skat.usc.edu!blarson
From: blarson@skat.usc.edu (Bob Larson)
Newsgroups: comp.arch
Subject: Re: FREQUENCY statements: fill a much-needed gap
Message-ID: <6107@oberon.USC.EDU>
Date: 11 Jan 88 02:03:15 GMT
References: <839@ima.ISC.COM> <28200085@ccvaxa> <1267@winchester.UUCP>
Sender: nobody@oberon.USC.EDU
Reply-To: blarson@skat.usc.edu (Bob Larson)
Organization: USC AIS, Los Angeles
Lines: 17

Programmers often don't realy know how their code will be used.  This
means that not only will their intuitive guesses on how frequently
sections of code will be used will be bad, but also they may not be
able to pick a reasonable set of cases to profile.  (Would you like to
see various versions of a product based on what profiles were fead to
the optomizer?)

Also, there are times where the most common case is not the one that
needs optimization.  Would you want a missle tracking system optimized
for the case where there are no incoming missles?  (Many such
real-time applictations are coded in assembler, but more and more are
now in high-level languages.)
--
Bob Larson	Arpa: Blarson@Ecla.Usc.Edu	blarson@skat.usc.edu
Uucp: {sdcrdcf,cit-vax}!oberon!skat!blarson
Prime mailing list:	info-prime-request%fns1@ecla.usc.edu
			oberon!fns1!info-prime-request