On Sun, 6 May 2012, Artem Bityutskiy wrote: > > I disagree. People generally don't fix their broken code just because it > > triggers warnings. The cases where GCC is genuinely confused are the > > minority -- and even if so, chances are the human reader of that code will > > also be. > > Aggressive opinion, nothing more. A patch which fixes the real issue a > better way would be way more respectful. I didn't trigger the issue, so I have nothing to fix. I would if it was me who did. And my opinion is based on experience. Please check the LMO archives for why Ralf added this option in the first place -- many years ago. It's probably recorded in the git repository too (I'm not sure if the option was added before or after we moved away from CVS, but in any case old change logs have been imported when our current repo was created). Maciej
