This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Moving towards GCC 3.1
- From: Richard Henderson <rth at redhat dot com>
- To: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
- Cc: pfeifer at dbai dot tuwien dot ac dot at, gcc at gcc dot gnu dot org
- Date: Wed, 26 Dec 2001 11:29:52 -0800
- Subject: Re: Moving towards GCC 3.1
- References: <10112261636.AA23204@vlsi1.ultra.nyu.edu>
On Wed, Dec 26, 2001 at 11:36:07AM -0500, Richard Kenner wrote:
> There are numerous types of patches that fix bugs that fall into neither
> of the above two categories:
>
> (1) Fixing existing testcase failures on a particular target.
> (2) Fixing build failures on a particular target.
Easily granted.
> (3) Fixing latent bugs
Not granted as a separate category. If it's a latent bug, then
it must fall into 1 or 2, or have a new test case.
> (4) Fixing documentation or code quality issues
Define "code quality issues". If you mean your "code cleanups that
must be reviewed because they invariably introduce new bugs" then I
do not agree. If you mean "arbitrarily changing whitespace" then I
do not agree.
> (5) Fixing bugs in proprietary test cases
It's funny, because I work with proprietary test suites all the time,
and about 2/3 of the time I manage to generate an independant test
case from problems seen there. More if you discount reload problems.
r~