> Does "efficiencyfy" map to "optimize"?
In common usage, yes, sure...
http://theory.csail.mit.edu/~randall/papers/abstracts/denali.html
is a very interesting paper, IMHO; here is a relevant excerpt
from its Introduction:
-- cut here --
Most programmers spend most of their day execut-
ing an edit-compile-debug loop; and most automatic code
generators (even so-called "optimizers") are designed to run
as part of a compiler that is used in this manner, and there-
fore are constrained by the requirement that they generate
hundreds, thousands, or millions of instructions per second.
Such a code generator has little hope of generating code that
will be good enough for our purpose. Consequently a great
deal is known about quickly generating indifferent code, and
very little is known about generating optimal code, which is
our goal. Indeed, the label "optimization" has been given to
a field that does not aspire to optimize but only to improve.
This misnomer presented a difficulty to Henry Massalin, who
invented the only other code generation technique we know
of that aimed at our goal [14]: the difficulty was that if Mas-
salin called his system an optimizer, people would assume
that it was only a code improver. So Massalin called his
system a superoptimizer. In our title, we have adopted his
nomenclature.
-- cut here --
Was pool usage optimized? Or superoptimized?? :)
-Ed
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 5 01:39:04 2007