Loop unroll fixes

[Joseph S. Myers]

On Fri, 14 Sep 2001, Daniel Berlin wrote:

> Your job, as a maintainer, is to review patches.

As a maintainer, this is not the case; every patch can be reviewed by at
least the twelve people with global write privileges and there is no
particular requirement on any one person to review a particular patch.

As a developer (of patches touching other areas of the compiler), we need
a patch tracking system to avoid patches getting lost.

As both, even trivial patches can fail to attract the necessary attention,
especially if they do need a global write maintainer or multiple
maintainers to look at them.  E.g.,
<URL: http://gcc.gnu.org/ml/gcc-patches/2001-06/msg01412.html > (a simple
patch to help i18n) still awaits review of the one-line patch to exgettext
(the C front end part is OK).  A lot of patches are, like this, largely
within one maintainer's competence but for trivial reasons involve changes
elsewhere requiring review from someone else as well.

-- 
Joseph S. Myers
jsm28@cam.ac.uk