On Thu, 8 Nov 2007, Ralf Baechle wrote: > > Yeah... If only GCC had no bugs and always had a clue of what to warn > > about... > > The least of all problems. It depends for whom I suppose. ;-) It is a pain when you have to stretch your imagination to rewrite a piece of source code GCC warns about unduly and both keep it readable and not make the generated binary worse... Especially where configuration-specific macros are involved. > As of 2.6.20-rc2-git2 we had 137 warnings in MIPS specific code of a total > of 218 for the kernel and 44 for modules - that's a insane 52%. And people > happily added more crappy code because they didn't not even _notice_ the > warnings some of which indeed were bugs. Well, adding no warnings should be the rule #1 and I can understand it is easier for you to enforce it by the means of -Werror. ;-) Maciej
