This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: egcs fixinc: This Time For Sure (tm)


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]