executable file size

[Jeffrey A Law]

  In message < 199709192019.NAA23099@atrus.synopsys.com >you write:
  > 
  > > We need a -Ospacen flag, where n is a number, were higher numbers mean
  > > make is smaller, and -Ospace99 means make it run slowly if you have
  > > to, but make it fit.  With such a flag, the compiler can serve those
  > > that have memory to burn, but want every last ounce of performance can
  > > get it, as well as people that pay $1 for every 1000 bytes.
  > ...
  > > What do others think?
  > 
  > Good idea in principle, especially for embedded systems.  In practice,
  > it will take a little time before this will be effective, and it requires
  > some thought.  For example, inlining in general trades space for speed,
  > but it may improve both space and speed (if the function is called from
  > only one place, or if the inlined code is smaller than the code for a call).
IMHO, just an -Ospace or -fspace is all we really need.  I don't think
we want to try and come up with 99 (or even 10) different levels of space
(or speed) optimizations.

Jeff