Re: Small update to reversed_comparison_code

[kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)]

    This does not compute. If it is very important then it would get fixed
    anyway.

Maybe yes, maybe no.  In a volunteer project like GCC, people tend to work
only on things they enjoy or (mostly in the case of the folks that work for
companies depending on GCC) they have to.  A bug that comes and goes like
this can be important, but it's going to be hard to get motivated to work on
it.  It becomes much easier to "blame" the person whose patch triggers it,
who probably isn't technically able to fix it.

    Forfcing the issue with a build breakage is tecnical extortion, and
    something that worries people a lot (including Mark and me!)

I do understand the concern, but GCC is a volunteer project, so motivation to
fix things is something that's not necessarily bad.  Sure, if this were a
commercial project with normal industrial management, this would be a very
bad thing, but the role of that management is precisely to make sure that
things like this don't fall on the floor.  In an unmanaged project there's
nobody to do that, so this sort of "extortion" has to play that role.