[PATCH] Fixing warnings revealed by gcc release build

[Vane, Edwin]

> 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?

- David