This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Beyond GCC 3.0: Summing Up
- To: mark at codesourcery dot com
- Subject: Re: Beyond GCC 3.0: Summing Up
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Date: Tue, 10 Jul 01 06:26:15 EDT
- Cc: gcc at gcc dot gnu dot org
It's just an ordering thing: if we can't get anyone to fix the latent
bug before checking in the patch, or as soon as the problem is
noticed, why do we think we can get someone to fix it afterwards?
For the first case, because it's easier to work on fixing something that's
visible in the top-of-tree sources than it is to have to make local changes
in order to even see a problem.
For the second, scheduling. It may often be the case that the person
needed to fix a latent problem that got exposed will be busy at the time
the patch that exposes it is approved, but has time to work on it later.