Re: Space Saving Compilers

pardo@june.cs.washington.edu (David Keppel)
10 Oct 90 20:41:52 GMT

          From comp.compilers
Related articles
Space Saving Compilers krish@hudson.cs.columbia.edu (1990-10-09)
Re: Space Saving Compilers wendt@ives.cs.colostate.edu (1990-10-10)
Re: Space Saving Compilers pardo@june.cs.washington.edu (1990-10-10)
| List of all articles for this month |
Newsgroups: comp.compilers
From: pardo@june.cs.washington.edu (David Keppel)
Keywords: code,optimize
Organization: University of Washington, Computer Science, Seattle
References: <1990Oct9.052008.12705@cs.columbia.edu>
Distribution: usa
Date: 10 Oct 90 20:41:52 GMT

The moderator writes:
>[If you want to make a unix kernel significantly smaller, turn off features
>and make tables smaller. Code optimizers don't make that much size
>difference. -John]


Alan Wendt notes that optimizers can be tuned for reducing
code size rather than reducing runtime. The paper he
references says that they sometimes got space savings on the
order of 30%.


See also:
%A Thomas Pittman
%T Two-Level Hybrid Interpreter/Native Code Execution for Combined
Space-Time Program Efficiciency
%D 1987
%J ACM SIGPLAN
%P 150-152


And Peter Deutsch's Smalltalk-80 implementation from ParcPlace
Systems gets 4:1 or more compression by using bytecodes and
generating n-code in to a code cache on demand.


;-D on ( Bittencodes ) Pardo
--
pardo@cs.washington.edu
        {rutgers,cornell,ucsd,ubc-cs,tektronix}!uw-beaver!june!pardo
[Good points, I was thinking of the sort of optimization you get with your
typical -O flag. -John]
--

Post a followup to this message

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