On June 18, Paul Vixie wrote:
> >   But is there any other way out of the GCC Bloat Syndrome?
> 
> sure there is.  look carefully at the collection of command line options
> that it takes to turn gcc into an ansi-only compiler with the few small
> gcc-isms that actually improve object code (like inline functions) and
> then make them into ./configure options for gcc itself.  this will take
> a few weeks of #ifdef'ing the various parts of gcc to avoid compiling
> all the extra bloat (nested function support comes to mind).  you'd get
> a gcc that was 2/3 the size, probably 3/4 the runtime, and no way to
> accidentally depend on some gcc-ism that would make your code unportable.
> 
> this would be a very popular move, not just in the *bsd community but for
> the entire gcc community.  and it would be less work than reviving pcc or
> writing something new.

  This is an interesting idea.  Is it practical?  Are the internals
documented (or readable) enough by "outside" people to facilitate such
an effort?

         -Dave

-- 
Dave McGuire                       "*BURRRP!*  Mmm...tastes like cannoli,
St. Petersburg, FL                    smells like garlic!" -Sridhar