Supported Chips

Jeffrey A Law law@cygnus.com
Thu Sep 30 23:58:00 GMT 1999


  In message < xdzoydv5c6.fsf@andros.cygnus.com >you write:
  > For GDB I've instituted a two-stage system for obsolescent code, where
  > for one release it's announced as obsolete, and if no one acts to save
  > it by the next release, then it's removed entirely.  This is so people
  > aren't misled into spending time maintaining bits that are actually
  > useless.  To merit this treatment, the configuration has to be pretty
  > thoroughly dead; in the Gould case for instance, I was able to find an
  > online "obituary" from when the last known live machine was turned off
  > a couple years ago.
Yea.  I'd like to see GCC put similar policies in place.  It's really not
worth people time to fix some of the long dead GCC ports.

GCC has ports which haven't been configurable for years (since gcc-2.0)
those would be the first in line to die (fx80, gmicro/tron, spur, tahoe).

Though ironically enough, we got a question from someone trying to build
the clipper port today...  Scary.

jeff




More information about the Gcc-patches mailing list