Contribution to egcs

[Jeffrey A Law]

  In message < Pine.BSI.4.02.9908012252480.16350-100000@pacifier.com >you write:
  > I would like to find a way the the redundant info was not written to the
  > .o files in the first place... perhaps an option for all the DWARF2 info
  > to be written to a projectname.dwf file, limit the redundncy in some
  > effecient way and modify the debugger to look for the dwarf info in that
  > project.dwf file rather than in the executable.  It might wind up being
  > DWARF3 or some such thing. It sounds like a lot of work.
It sounds like a lot of work down the wrong direction.  I strongly recommend
you pursue removing redundant stuff in the linker, possibly using additional
information provided by the compiler (which is how stabs does it).



  > Another thing that is of interest to me is implementation of precompiled
  > headers for C/C++.  Has anyone done a feasibility probe on this for egcs?
  > I am certain that for some projects this would speed compiliation quite a
  > bit.
Not really.  Or more correctly, there's some very tricky issues in the area
of precompiled headers and by using a sane design for your code and header
files you can avoid the problem in the first place.

Furthermore, if you're optimizing, the vast majority of the compile time is
in the optimizer.

I also suggest you only try to tackle one problem at a time.  

jeff