Newsgroups: | comp.compilers |
From: | hrubin@pop.stat.purdue.edu (Herman Rubin) |
Organization: | Purdue University Statistics Department |
Date: | Fri, 11 Dec 1992 14:38:05 GMT |
References: | 92-12-029 92-12-040 92-12-043 |
Keywords: | optimize, comment |
bill@amber.csd.harris.com (Bill Leonard) writes:
>I prefer not to write my code for a particular compiler's optimization
>algorithms.
However, the speed of the executed code does depend on how the compiler
assigns branches to fall-through and transfer. Thus, 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.
--
Herman Rubin, Dept. of Statistics, Purdue Univ., West Lafayette IN47907-1399
Phone: (317)494-6054
hrubin@snap.stat.purdue.edu (Internet, bitnet)
{purdue,pur-ee}!snap.stat!hrubin(UUCP)
[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]
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.