Re: static estimation of conditional branches?

henry@zoo.toronto.edu (Henry Spencer)
Fri, 11 Dec 1992 17:41:18 GMT

          From comp.compilers

Related articles
[2 earlier articles]
Re: static estimation of conditional branches? bill@amber.csd.harris.com (1992-12-09)
Re: static estimation of conditional branches? tom@derby.cs.wisc.edu (1992-12-09)
Re: static estimation of conditional branches? tsych@sedona.intel.com (1992-12-09)
Re: static estimation of conditional branches? hagerman@ece.cmu.edu (1992-12-09)
Re: static estimation of conditional branches? bill@amber.csd.harris.com (1992-12-10)
Re: static estimation of conditional branches? hrubin@pop.stat.purdue.edu (1992-12-11)
Re: static estimation of conditional branches? henry@zoo.toronto.edu (1992-12-11)
Re: static estimation of conditional branches? idacrd!desj@uunet.UU.NET (1992-12-12)
Re: static estimation of conditional branches? jfisher@hplabsz.hpl.hp.com (1992-12-11)
Re: static estimation of conditional branches? chased@rbbb.Eng.Sun.COM (1992-12-12)
Re: static estimation of conditional branches? glew@pdx007.intel.com (1992-12-12)
Re: static estimation of conditional branches? henry@zoo.toronto.edu (1992-12-13)
Re: static estimation of conditional branches? hrubin@pop.stat.purdue.edu (1992-12-13)
[4 later articles]
| List of all articles for this month |
Newsgroups: comp.compilers
From: henry@zoo.toronto.edu (Henry Spencer)
Organization: U of Toronto Zoology
Date: Fri, 11 Dec 1992 17:41:18 GMT
Keywords: optimize, design
References: 92-12-029 92-12-046

hrubin@pop.stat.purdue.edu (Herman Rubin) writes:
>... the programmer should have some way of communicating this, and other,
>frequency considerations to the compiler. As far as I know, this has not
>been done since the "FREQUENCY" statement in fairly early Fortran.
>[As I recall, Fortran II dropped FREQUENCY because it was infrequently
>used and made little difference. I've heard that it may even have been
>implemented backwards and nobody noticed. -John]


The other problem that occurs with such facilities is that programmer
intuition is notoriously unreliable about such things.


Now, if you amend Herman's statement to "the *profiler* should have some
way of communicating this...", I'd agree... and observe that there are
already compilers that will accept profiler data and exploit it for
optimization. I don't know whether they do this particular optimization,
but I wouldn't be surprised.
--
Henry Spencer @ U of Toronto Zoology, henry@zoo.toronto.edu utzoo!henry
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.