[PATCH] Fixing warnings revealed by gcc release build

[Dmitri Gribenko]

On Wed, Jan 30, 2013 at 4:55 PM, Vane, Edwin <edwin.vane at intel.com> wrote:
>> Why is that heavy handed? If the warning is bad there's no reason to
>> hold us to it.
>
> I admit I'm complaining about this warning because I'd like to see my continuous integration builder turn green instead of yellow and I build with both clang and gcc. As for heavy-handed, I only meant that we'd have to turn off this potentially useful warning for the entire build. The bug in gcc is for empty {} but the missing field initializers warning could still be useful no? Or should we just disable it for gcc and let the clang build catch the problems?

If this is the only false positive, I think it is worth working around
the warning.

Dmitri

-- 
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/