This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: egcs fixinc: This Time For Sure (tm)
- To: egcs at cygnus dot com, korbb at datadesign dot com
- Subject: Re: egcs fixinc: This Time For Sure (tm)
- From: mrs at wrs dot com (Mike Stump)
- Date: Wed, 4 Mar 1998 17:27:28 -0800
Sometimes when I put new dangerous code in the compiler, I leave the
old stuff in, and run the new stuff in parallel, and compare the
results. I then AI match the results, and use the old stuff if they
differ in ways I don't expect. If they differ in ways I expect or are
the same, I use the new stuff.
After a suitable time span, I then rip out all the old code.
(Yes folks, we can practice software fault tolerance. :-))
Fixincludes sounds like one of those things were doing this would be
fairly easy. Also, once checked you can add the triplet to a list of
known good systems (to regain the speed) to mitigate the slowdown
doing this would otherwise cause.
Just a thought.